Wednesday 13 March 2013

Create a Windows Server 2003 Sysprep Package in SCCM 2012

  1. Download Sysprep - http://www.microsoft.com/en-gb/download/details.aspx?id=14830
  2. Extract contents of downloaded EXE by using switch /x:<path to extract to>
  3. From Extracted EXE find SP2QFE directory
  4. Extract the deploy.cab to a network share accessible by SCCM
  5. Create a Package in SCCM
    1. Give it a name, descritption etc.
    2. Tick this package contains source files and point it to the above network share
    3. Select Do not create a program
  6. Distribute the Package
  7. Edit the Server 2003 Build and Capture Task sequence
  8. In the Capture the Reference Machine Task Group. Add Images > Install Deployment Tools
  9. Select the Sysprep Package we just created

Thursday 19 April 2012

Exchange SP2 Rollup 1 and CAS members

Check the following Registry keys are present before updating a CAS member to SP2 Rollup 1.
If they are not present then OWA will be broken with missing files.


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns]
@=""

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.E2010]
"CustomPSSnapInType"="Microsoft.Exchange.Management.PowerShell.AdminPSSnapIn"
"ApplicationBase"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin"
"AssemblyName"="Microsoft.Exchange.PowerShell.Configuration, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
"Description"="Admin Tasks for the Exchange Server"
"ModuleName"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.PowerShell.Configuration.dll"
"PowerShellVersion"="1.0"
"Vendor"="Microsoft Corporation"
"Version"="14.0.0.0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.PowerShell.Setup]
"CustomPSSnapInType"="Microsoft.Exchange.Management.PowerShell.SetupPSSnapIn"
"ApplicationBase"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin"
"AssemblyName"="Microsoft.Exchange.PowerShell.Configuration, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
"Description"="Setup Tasks for the Exchange Server"
"ModuleName"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.PowerShell.configuration.dll"
"PowerShellVersion"="1.0"
"Vendor"="Microsoft"
"Version"="14.0.0.0"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\Microsoft.Exchange.Management.Powershell.Support]
"CustomPSSnapInType"="Microsoft.Exchange.Management.Powershell.Support.SupportPSSnapIn"
"ApplicationBase"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin"
"AssemblyName"="Microsoft.Exchange.Management.Powershell.Support, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
"Description"="Support Tasks for the Exchange Server"
"ModuleName"="C:\\Program Files\\Microsoft\\Exchange Server\\V14\\bin\\Microsoft.Exchange.Management.Powershell.Support.dll"
"PowerShellVersion"="1.0"
"Vendor"="Microsoft Corporation"
"Version"="14.0.0.0"

Wednesday 18 April 2012

Installing CAS Server Prerequisites for Exchange 2010 SP2

Launch an elevated Powershell.

Import-Module ServerManager
Add-WindowsFeature Web-WMI

CSV Report for Services on a PC

Fire up PowerShell:
Get-Service * | Sort ServiceType | Export-CSV

To be a bit more specific on what to report on:
Get-Service * | Sort DisplayName | select displayname, status | Export-CSV

Tuesday 17 April 2012

Exchange 2010 SP2 Schema Upgrade

I have an existing Exchange 2010 SP1 installation.  
Here is how I applied the Schema update for Exchange SP2.

  • Find out which DC is the Schema Master
  • Stick Exchange SP2 somewhere on the network which is accessible by the DC
  • Unpack the SP2 update
Run from the unpacked Exchange SP2 location...
  • setup /PrepareSchema
It will throw up this prompt which is OK.

"Welcome to Microsoft Exchange Server 2010 Unattended Setup
Setup will continue momentarily, unless you press any key and cancel the
installation. By continuing the installation process, you agree to the license
terms of Microsoft Exchange Server 2010.
If you don't accept these license terms, please cancel the installation. To
review the license terms, please go to
http://go.microsoft.com/fwlink/?LinkId=150127&clcid=0x409/
Press any key to cancel setup................"

Wait for a success message:
"Extending Active Directory schema                         COMPLETED"

After that wait for an AD Replication to happen.
Then run the following.

  • setup /PrepareAD
The same prompts will pop up and you should get the following success messages.
 "Organization Preparation                                  COMPLETED"

Again, wait for an AD replication to happen.
Now run the final command:

  • setup /prepareDomain:<your.domain.name>
You'll get this success message:
"Prepare Domain Progress                                   COMPLETED"


Wait for a final AD replication.

You can then check if the schema update successfully by checking the following in ADSIEdit:

  • Value of rangeUpper attribute of ms-Exch-Schema-Version-Pt object in Schema NC has changed to 14732.
  • objectVersion attribute of Organization container in Configuration NC should be a value of 14247.  
  • objectVersion attribute on Microsoft Exchange System Objects container in Domain NC should be unchanged at value of 13040 which is correct.

Find Exchange 2010 Organization Name

Launch the Exchange 2010 Management Shell and run this:
Get-OrganizationConfig | select name

Find Schema Master in Windows Server 2008 R2

To find out who has the Schema FSMO in Windows 2008 R2:

  • On a DC open an elevated CMD prompt
  • Navigate to C:\WINDOWS\System32
  • Run the following command: regsvr32 schmmgmt.dll
  • A window should pop-up confirming if it registered correctly
  • Open MMC
  • Add the Active Directory Schema snap-in via the File menu
  • Right Mouse click on the 'Active Directory Schema' node and click on Operations Master...
  • That should bring up a window telling you the Current Schema Master
Simples.