Set Active Directory user property's with Powershell

Need to edit a user property here's how:

To set the Dail-in property to deny access, you look for the corresponding value, in this case:

"msNPAllowDailin" which is set to TRUE.

In Powershell you type:set-ADUser username -Replace @{msnpallowdialin=$false}

Now when you look at the same value in the attribute editor it displays FALSE.

I haven't tried it but i guess everything that has a value can be changed or edited by the same command.

If you know some others, or disagree let me know.

Get system up time script and alternative ways

Save as a ps1 script, and run.

$computer = "computername"

$lastboottime = (Get-WmiObject -Class Win32_OperatingSystem -computername $computer).LastBootUpTime

$sysuptime = (Get-Date) – [System.Management.ManagementDateTimeconverter]::ToDateTime($lastboottime) 
  
Write-Host "$computer has been up for: " $sysuptime.days "days" $sysuptime.hours "hours" $sysuptime.minutes "minutes" $sysuptime.seconds "seconds" 

Outputs like:

PS D:\_DATA\Scripts> .\Uptime.ps1

computername has been up for:  71 days 4 hours 26 minutes 50 seconds

Alternatives:

1. Go to "Start" -> "Run".

2.  Write "CMD" and press on "Enter" key.

3. Write the command systeminfo | find "up time" and press on "Enter" key.

1. Go to "Start" -> "Run".

2.  Write "CMD" and press on "Enter" key.

3.  Write the command "net statistics server" and press on "Enter" key.

4.  The line that start with "Statistics since …" provides the time that the server was up from.

•   The command "net stats srv" can be use instead.

Uptime.exe Tool Allows You to Estimate Server Availability with Windows NT 4.0 SP4 or Higher

Source

Alternate source

Powershell 407 proxy authentication required

When trying to run Get-Software.ps1, you may receive an error message:

Do you want to Download PSExec ?
[Y] Yes  [N] No  [?] Help (default is "Y"): y
Exception calling "DownloadFile" with "2" argument(s): "The remote server retur
ned an error: (407) Proxy Authentication Required."
At D:\_DATA\Downloads\Hydrationkit\Build\Modules\Software.psm1:83 char:33
+                                 $WebClient.DownloadFile($Source, $Destination
)
+                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : WebException

Run these commands to send your current credentials

$proxy = New-Object System.Net.WebClient

$Proxy.Proxy.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials

After this the script runs fine:

Do you want to Download PSExec ?
[Y] Yes  [N] No  [?] Help (default is "Y"):

Do you want to Download SetupCA ?
[Y] Yes  [N] No  [?] Help (default is "Y"):

Do you want to Download Windows Assessment and Deployment Kit (ADK) for
Windows® 8 ?
[Y] Yes  [N] No  [?] Help (default is "Y"):

Source

New-exchangecertificate for Exchange EDGE 2010

Do this after office hours or in a service window, because the risk exists that mail flow may come to a halt because the edgesync subscription certificate don't match anymore. I found out the hard way.

Generate a new certificate request:

$data = New-ExchangeCertificate -GenerateRequest -SubjectName "cn=mx03.domain.com" -domainname mx03.domain.com, sr-XXXXX.domain.lan, sr-XXXXX -friendlyname mx03.domain.com -PrivateKeyExportable $true
Set-Content -Path "c:\Temp\mailcert.req" -Value $Data

Import the request into the PKI website http://servername/certsrv

Request a new Certificate

Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file

Enter the request code and press Submit

On the PKI environment Issue the requested certificate and export the new certificate.

On the EDGE server copy the certificate to a folder.

To import the certificate in Powershell:

Import-ExchangeCertificate -FileData ([Byte[]]$(Get-Content -Path c:\certificates\ExportedCert.cer -Encoding byte -ReadCount 0))

Check the thumbprint to use in the next commandlet:

Get-exchangecertificate | fl

Use the thumbprint in the following line:

Enable-ExchangeCertificate -Thumbprint 5113ae0233a72XXXXXXXXXXXXXXXX8675333d010e -Services SMTP

Then recreate the EdgeSync Subcription

new-edgesyncsubcription -filepath "C:\temp\filename.xml"

Export the XML file to your CAS server and create a new Edgesync subscription.

The problem right now is we do not refresh the certificate used by ADAM when issue a new subscription, so if you have created a new certificate, we keep presenting the old one. Ok, so here's what you need to do to get ADAM to present the new one:

 

1. On the Hub, Remove the Subscription

2. On the Edge, Remove the cert used by ADAM to establish secure

connections. You can do this by following the following steps:

• a. Open up an empty mmc console (Run -> mmc)
• b. Select File -> Add / Remove Snap-in
• c. Hit Add
• d. Select "Certificates" from the List of Snap-Ins available, and
• hit Add.
• e. Select "Service Account" on the "Certificates Snap-In" page,
• click next.
• f. Select "Local Computer" on the "Select Computer" page, click
• next.
• g. Select "Microsoft Exchange ADAM" from the list of services,
• click Finish.
• h. Close the "Add Snap-in" dialog.
• i. Navigate to "Certifcates – Service" ->
• "ADAM_MSExchange\Personal" -> Certificates
• j. You should see a single certificate here. Remove it.

3. On the Edge, Unsubscribe, then create a new subscription file

(you should see a new certificate show up at this point on the ADAM cert container from the step above) by calling new-edgesubscription

 

New-EdgeSubscription -FileName "Path to file".xml
 

4. Re-start the "Microsoft Exchange ADAM" service.

5.Export the file to the Hub server.

6.On the Hub server import the new subscription.
7.Create a new Edge subscription in the EMC

Then you have to wait a few minutes.

To check if synchronization works run;

start-edgesynchronization
test-edgesynchronization

Sync Folders and files with Powershell and send notification email

I needed a way to sync some files and folders to another disc, as Allwaysync only permits less than 40.000 items per sync.
I came across a nice script from here.

But it did not exactly do what i needed it to do so adjustments were made.
I didnt need it to check the destination against the source, so got rid of that,
and made a way for it to email me the results as it had
finished comparing and syncing.

The script looks like this now:

Param($Source,$Destination)
function Get-FileMD5 {
    Param([string]$file)
    $mode = [System.IO.FileMode]("open")
    $access = [System.IO.FileAccess]("Read")
    $md5 = New-Object System.Security.Cryptography.MD5CryptoServiceProvider
    $fs = New-Object System.IO.FileStream($file,$mode,$access)
    $Hash = $md5.ComputeHash($fs)
    $fs.Close()
    [string]$Hash = $Hash
    Return $Hash
}
# Source from http://bsonposh.com/archives/231

$logfile = "C:\temp\foldersync.log"

function Copy-LatestFile{
     Param($File1,$File2,[switch]$whatif)
     $File1Date = get-Item $File1 | foreach-Object{$_.LastWriteTimeUTC}
     $File2Date = get-Item $File2 | foreach-Object{$_.LastWriteTimeUTC}
     if($File1Date -gt $File2Date)
     {
         write-output "$File1 is Newer… Copying…" | out-file $logfile -Append
         if($whatif){Copy-Item -path $File1 -dest $File2 -force -whatif}
         else{Copy-Item -path $File1 -dest $File2 -force}
     }
     else
     {
         write-output "$File2 is Newer… Copying…" | out-file $logfile -Append
         if($whatif){Copy-Item -path $File2 -dest $File1 -force -whatif}
         else{Copy-Item -path $File2 -dest $File1 -force}
     }
     write-output | out-file $logfile
}

if(!(test-Path $Destination))
{
     New-Item $Destination -type Directory -force | out-Null
}

# Getting Files/Folders from Source and Destination
$SrcEntries = Get-ChildItem $Source -Recurse -Force
$DesEntries = Get-ChildItem $Destination -Recurse -Force

# Parsing the folders and Files from Collections
$Srcfolders = $SrcEntries | Where-Object{$_.PSIsContainer}
$SrcFiles = $SrcEntries | Where-Object{!$_.PSIsContainer}
$Desfolders = $DesEntries | Where-Object{$_.PSIsContainer}
$DesFiles = $DesEntries | Where-Object{!$_.PSIsContainer}

# Checking for Folders that are in Source, but not in Destination
foreach($folder in $Srcfolders)
{
     $SrcFolderPath = $source -replace "\\","\\" -replace "\:","\:"
     $DesFolder = $folder.Fullname -replace $SrcFolderPath,$Destination
     if($DesFolder -ne ""){
         if(!(test-path $DesFolder))
         {
             write-output "Folder $DesFolder Missing. Creating it!" | out-file $logfile -Append
             new-Item $DesFolder -type Directory | out-Null
         }
     }
}

# Checking for Files that are in the Source, but not in Destination
foreach($entry in $SrcFiles)
{
     $SrcFullname = $entry.fullname
     $SrcName = $entry.Name
     $SrcFilePath = $Source -replace "\\","\\" -replace "\:","\:"
     $DesFile = $SrcFullname -replace $SrcFilePath,$Destination
     if(test-Path $Desfile)
     {
         $SrcMD5 = Get-FileMD5 $SrcFullname
         $DesMD5 = Get-FileMD5 $DesFile
         If($srcMD5 -ne $desMD5)
         {
             write-output "The Files MD5′s are Different… Checking Write Dates" | out-file $logfile -Append
             write-output $SrcMD5 | out-file $logfile
             write-output $DesMD5 | out-file $logfile
             Copy-LatestFile $SrcFullname $DesFile
         }
     }
     else
     {
         write-output "$Desfile Missing… Copying from $SrcFullname" | out-file $logfile -Append
         copy-Item -path $SrcFullName -dest $DesFile -force
     }
}

$smtpto = "user@domain.com"
$smtpfrom = "FolderSync@domain.com"
$messagesubject = "FolderSync results $finishtime"
$smtpServer = "smtp.domain.com"


out-file $Logfile -Append

$finishTime = get-date -format "dd-MM-yy HH-mm"
"Backup script finished at $finishTime" | out-file $logFile -Append -Force

$message = New-Object System.Net.Mail.MailMessage $smtpfrom, $smtpto
$message.Subject = $messageSubject
$message.IsBodyHTML = $false
$finished = get-content $LogFile
$message.Body = ( $Finished | out-string )
$message.Body = $Finished
write-host 'Sending email'
$smtp = New-Object Net.Mail.SmtpClient($smtpServer)
$smtp.Send($message)
Write-Host "Email sent"

remove-item $Logfile


After this you can schedule it in task manager:

powershell -command "& 'E:\path to script\scriptname.ps1 X:\source Y:\destination' "

Sending email with powershell fails, 5.7.1 Client not authenticated

The error powershell throws at you:

Exception calling “Send” with “1″ argument(s): “The SMTP server requires a secure connection or the client was not authenticated. The server response was: 5.7.1 Client was not authenticated”

When using the following:

#Send email message

$smtp = New-Object Net.Mail.SmtpClient($smtpServer)

Needs another line and becomes this:

#Send email message

$smtp = New-Object Net.Mail.SmtpClient($smtpServer)

$smtp.UseDefaultCredentials = $true

Email delivers correctly.

Install Exchange 2010 Prerequisites on Windows 7 with Powershell (CMD)

Scripting your IIS and .NET 3.5 prerequisites for Exchange 2010 on Windows 7:

IIS:

dism /online /enable-feature /featurename:IIS-WebServerRole  /featurename:IIS-WebServerManagementTools /featurename:IIS-IIS6ManagementCompatibility /featurename:IIS-Metabase /featurename:IIS-LegacySnapIn

.NET 3.5:

Write-Host "Installing .Net Framework 3.5, do not close this prompt..." 
                    DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:$LocalSource | Out-Null  
                    $Result = Dism /online /Get-featureinfo /featurename:NetFx3 
                    If($Result -contains "State : Enabled") 
                    { 
                        Write-Host "Install .Net Framework 3.5 successfully." 
                    } 
                    Else 
                    { 
                        Write-Host "Failed to install Install .Net Framework 3.5,please make sure the local source is correct." 
                    }

In case the above doesn't work, you can try:

DISM /Online /Enable-Feature /FeatureName:NetFx3

Source

Lync 2010 - Revoke a User Certificate

Lync 2010 - Revoke a User Certificate

This one is more important than you may think. If you disable an AD account, and permit users to save their username/password, they will still be able to use Lync! A lot of people don't know this and it creates an interesting discussion with the security officer.

Revoke-CsClientCertificate "Username"

Source

Convert Legacy mailbox to User mailbox

If you happen to have a Legacy Mailbox on an Exchange 2010 server, you can upgrade or convert it to a User Mailbox by using the shell command:

Set-Mailbox -identity Alias -ApplyMandatoryProperties


After executing the command, the mailbox should be converted from Legacy to user in about 20 seconds.

How to find the version of your Lync Server 2010

Check this once in a while to see if you're missing Lync 2010 "CU" updates.

Get-WmiObject -query 'select * from win32_product' | where {$_.name -like "Microsoft Lync Server*"} | foreach {$_}

Or:

Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* |  ?{$_.DisplayName -like “*Lync Server*”} | Sort-Object DisplayName | Select DisplayName, DisplayVersion, InstallDate | Format-Table -AutoSize

Output:

DisplayName                                         DisplayVersion InstallDate
-----------                                         -------------- -----------
Microsoft Lync Server 2010, Administrative Tools    4.0.7577.190   20130131
Microsoft Lync Server 2010, Application Host        4.0.7577.0     20130201
Microsoft Lync Server 2010, Audio Test Service      4.0.7577.0     20130201
Microsoft Lync Server 2010, Best Practices Analyzer 4.0.7577.118   20131022
Microsoft Lync Server 2010, Conferencing Server     4.0.7577.709   20141214
Microsoft Lync Server 2010, Core Components         4.0.7577.709   20141214
Microsoft Lync Server 2010, Core Management Server  4.0.7577.0     20130517
Microsoft Lync Server 2010, Front End Server        4.0.7577.707   20141214
Microsoft Lync Server 2010, Mobility Service        4.0.7577.217   20130919
Microsoft Lync Server 2010, Reach Fonts             4.0.7577.0     20130201
Microsoft Lync Server 2010, Resource Kit Tools      4.0.7577.197   20130808
Microsoft Lync Server 2010, Web Components Server   4.0.7577.231   20141214
Microsoft Lync Server 2010, Web Conferencing Server 4.0.7577.199   20130201

 
 PS C:\Lync> Get-WmiObject -query 'select * from win32_product' | where {$_.nam

 
 Name                                                Version
----                                                -------
Microsoft Lync Server 2010, Mobility Service        4.0.7577.217
Microsoft Lync Server 2010, Resource Kit Tools      4.0.7577.197
Microsoft Lync Server 2010, Web Components Server   4.0.7577.231
Microsoft Lync Server 2010, Web Conferencing Server 4.0.7577.199
Microsoft Lync Server 2010, Core Components         4.0.7577.709
Microsoft Lync Server 2010, Best Practices Analyzer 4.0.7577.118
Microsoft Lync Server 2010, Core Management Server  4.0.7577.0
Microsoft Lync Server 2010, Audio Test Service      4.0.7577.0
Microsoft Lync Server 2010, Application Host        4.0.7577.0
Microsoft Lync Server 2010, Administrative Tools    4.0.7577.190
Microsoft Lync Server 2010, Reach Fonts             4.0.7577.0
Microsoft Lync Server 2010, Front End Server        4.0.7577.707
Microsoft Lync Server 2010, Conferencing Server     4.0.7577.709

 
 PS C:\Lync> $PSVersionTable

 Name                           Value
----                           -----
CLRVersion                     2.0.50727.5485
BuildVersion                   6.1.7601.17514
PSVersion                      2.0
WSManStackVersion              2.0
PSCompatibleVersions           {1.0, 2.0}
SerializationVersion           1.1.0.1
PSRemotingProtocolVersion      2.1

CU update list:

Lync 2010

CU #	Description
CU1	http://support.microsoft.com/?kbid=2467763 Description of the cumulative update package for Lync 2010: January 2011 (Version: 4.0.7577.108)
CU2	http://support.microsoft.com/?kbid=2496325 Description of the cumulative update package for Lync 2010: April 2011 (Version: 4.0.7577.253)
CU3	http://support.microsoft.com/kb/2551268 Description of the cumulative update package for Lync 2010: May 2011 (Version: 4.0.7577.280)
CU4	http://support.microsoft.com/?kbid=2571543 Description of the cumulative update package for Lync 2010: July 2011 (Version: 4.0.7577.314)
CU5	http://support.microsoft.com/?kbid=2514982 Description of the cumulative update package for Lync 2010: November 2011 (Version: 4.0.7577.4051)
CU6	http://support.microsoft.com/kb/2670326 Description of the cumulative update package for Lync 2010: February 2012 (Version: 4.0.7577.4072)
CU7	http://support.microsoft.com/kb/2701664 Description of the cumulative update package for Lync 2010: June 2012 (Version: 4.0.7577.4103)
CU8	http://support.microsoft.com/kb/2737155 Description of the cumulative update package for Lync 2010: October 2012 (Version: 4.0.7577.4356)
CU9	http://support.microsoft.com/kb/2791382 Description of the cumulative update package for Lync 2010: March 2013 (Version: 4.0.7577.4378)
CU10	http://support.microsoft.com/kb/2815347 Description of the cumulative update package for Lync 2010: April 2013 (Version: 4.0.7577.4384)
CU11	http://support.microsoft.com/kb/2842627 Description of the cumulative update package for Lync 2010: July 2013 (Version: 4.0.7577.4398)
CU12	http://support.microsoft.com/kb/2884632 Description of the cumulative update package for Lync 2010: October 2013 (Version: 4.0.7577.4409)
CU13	http://support.microsoft.com/kb/2912208 Description of the cumulative update package for Lync 2010: January 2014 (Version: 4.0.7577.4419)

Lync Server 2010

CU#	Description
CU1	http://support.microsoft.com/kb/2467775 Description of the cumulative update for Lync Server 2010, Core Components: January 2011 (Version: 4.0.7577.108)
CU2	http://support.microsoft.com/kb/2500442 Description of the cumulative update for Lync Server 2010: April 2011 (Version: 4.0.7577.137)
CU3	http://support.microsoft.com/kb/2571546 Description of the cumulative update for Lync Server 2010: July 2011 (Version: 4.0.7577.166)
CU4	http://support.microsoft.com/kb/2514980 Description of the cumulative update for Lync Server 2010: November 2011 (Version: 4.0.7577.183)
CU5	http://support.microsoft.com/kb/2670352 Description of the cumulative update for Lync Server 2010: February 2012 (Version: 4.0.7577.190)
CU6	http://support.microsoft.com/kb/2701585 Description of the cumulative update for Lync Server 2010: June 2012 (Version: 4.0.7577.199)
CU7	http://support.microsoft.com/kb/2737915 Description of the cumulative update for Lync Server 2010: October 2012 (Version: 4.0.7577.203)
CU8	http://support.microsoft.com/kb/2791381 Description of the cumulative update for Lync Server 2010: March 2013  (Version: 4.0.7577.216)
CU9	http://support.microsoft.com/kb/2860700 Description of the cumulative update for Lync Server 2010: July 2013 (Version: 4.0.7577.217)
CU10	http://support.microsoft.com/kb/2889610 Description of the cumulative update for Lync Server 2010: October 2013  (Version: 4.0.7577.223)
CU11	http://support.microsoft.com/kb/2909888 Description of the cumulative update for Lync Server 2010: January 2014 (Version: 4.0.7577.225)

  




Source 1
Source 2