Hi I'm having issues with adding a new Site System Server with Powershell

Command I Use is  New-CMSiteSystemServer -ServerName "FQDN to new server" -SiteCode "SiteCode"

If the server i specify exist in AD and Configuration Manger (as a client), powershell crashes with the errors below.
If the server i specify is a dummy name that doesn't exist, everything works smooth.

I does how ever work to add the server as a Site Server within the SCCM Console

I have tested it on my LAB running 2012 R2 (no CU's) and that worked fine.
Once i had installed CU2 it started to crash, have not tested it with CU1.

Server is running SCCM 2012 R2 and SQL 2012

Anyone having similar issues?

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    powershell.exe
  Application Version:    6.3.9600.16384
  Application Timestamp:    5215ef23
  Fault Module Name:    clr.dll
  Fault Module Version:    4.0.30319.33440
  Fault Module Timestamp:    520038bd
  Exception Code:    c0000005
  Exception Offset:    000000000017aa32
  OS Version:    6.3.9600.2.0.0.272.79
  Locale ID:    1044
  Additional Information 1:    3bcf
  Additional Information 2:    3bcf0070fc3d9dc52c3b6b54a089ff89
  Additional Information 3:    72e1
  Additional Information 4:    72e1e0ed4a58b7b5573ed30ef4fef17a



Hi,

Based on the Syntax,  please try to use <String> after the parameter -ServerName.

New-CMSiteSystemServer -ServerName <String> -SiteCode <String> [-AccountName <String> ] [-EnableProxy <Boolean> ] [-FdmOperation <Boolean> ] [-ProxyAccessAccount <IResultObject> ] [-ProxyServerName <String> ] [-ProxyServerPort <UInt32> ] [-PublicFqdn <String> ] [-UseSiteServerAccount] [-Confirm] [-WhatIf] [ <CommonParameters>]

For example:

PS C:\> New-CMSiteSystemServer -ServerName "ContosoSvr02" -SiteCode "CM2"

New-CMSiteSystemServer

http://technet.microsoft.com/en-us/library/jj821732(v=sc.20).aspx

Same error when using servername only as in your example.

If i turn of the server i'm trying to add it will succeed.

I have the same issue.

Brand new Hierarchy built directly with CU2 and as soon as I use the New-CMSiteSystemServer PowerShell crashes. Other CM Cmdlets work fine just not the CMSiteSystemServer one

As you mentioned above I have tested that it succeeds when the target server is down.

Can anyone verify that this is CU2 issue ?

I have received information that Microsoft is aware of the issue and that a solution will posted here when it is available.

I can confirm that I have the same issue on Windows Server 2012 R2 with CM12R2 -> upgraded to CU1 then CU2.

We have the same issue a one of our customers, any idea when it's going to be fixed.

If the Cmdlet is broken, the best way to give your feedback to Microsoft is by using Connect and file a Bug.

https://connect.microsoft.com/

Hotfix has been released by Microsoft

http://support.microsoft.com/kb/2984644

• Marked as answer by Kenneth82 5 hours 9 minutes ago