Microsoft System Center Configuration Manager 2012–unattended installation of Sites
|
by David O'Brien on 01/17/2012 | 0 Comments | 1,313 Views
|
There’s a lot that changed in ConfigMgr2012 (e.g. Client Log Files ), but also inter-site communication. Most of it is now done via SQL replication and not only via inbox/outbox replication.
According to Microsoft, also the way we now have to install ConfigMgr sites has changed. In SCCM 2007 one could use an ini file to install primary and secondary sites (earlier article: Install Secondary Site unattended).
I asked a lot of Microsoft guys and they all said that it’s not possible anymore to script anything in ConfigMgr2012.
Script to install
Thanks to Rod Trent (ConfigMgr 2012 tip: grab the Unattended Installation file during setup) I came upon the “ConfigMgrAutoSave.ini” which has some valuable information regarding the installation process of ConfigMgr sites.
As in 2007, the /script switch of setup.exe still works in ConfigMgr2012.
The command-line would look like this:
%installsourcefolder%\setup.exe /script "%PathToINI% /NoUserInput
The ini looks like this:
1: [Identification] 2: Action=InstallSecondarySite 3: 4: [Options] 5: SiteCode=BLA 6: SiteName=BLA 7: SMSInstallDir=C:\Microsoft Configuration Manager 8: ParentSiteCode=011 9: ParentSiteServer=test.osd.local 10: AddressType=MS_LAN 11: UseFQDN=1 12: 13: [SQLConfigOptions] 14: SQLServerName=test2.osd.local 15: DatabaseName=CONFIGMGRSEC\CM_BLA 16: InstallSQLExpress=1 17: SQLExpressCollation=Latin1_General_CI_AS 18: SQLServicePort=1433 19: SQLSSBPort=4022 20: 21: [HierarchyExpansionOption] 22: ParentSiteNumber=1 23: ParentSQLServerName=test.osd.local 24: ParentDatabaseName=CM_BLO 25: ParentSQLServerSerializedCertificate= *deleted for privacy* 26: ParentSQLServerMachineSerializedCertificate= *deleted for privacy* 27: ParentSiteServiceExchangeKey= *deleted for privacy* 28: ParentSQLServerSSBPort=4022 29: 30: [Bootstrap] 31: Action=Install 32: SetupPath=\SMSSETUP\bin\x64\SetupWPF.exe 33: BuildNumber=7678 34: InstallMapPath=\SMSSETUP\install.map 35: SecurityMode=Advanced 36: SetupSourcePath=C:\ConfigMgr2012_DEU37: State=Looking for the SMS CD...
38: StartTime=1326713845 39: WorkingDir=This installation runs through until trying to communicate with the parent primary site. This fails and such the whole installation fails.
I believe this is because the primary site doesn’t know that there is a new secondary site being installed.
The same kind of *.ini file can be used to install primary sites, but I didn’t test that as the customer wants to install secondary sites (up to 150) unattended.
I would love to get your ideas on this topic and see if anyone can figure this out.
[Update]
Primary Site script installation
Installing a primary site would work with this “ConfigMgrAutoSave.ini”:
1: [Identification] 2: Action=InstallPrimarySite 3: 4: [Options] 5: ProductID=%ProductKey% 6: SiteCode=011 7: SiteName=011 8: SMSInstallDir=D:\Microsoft Configuration Manager 9: SDKServer=test.osd.local 10: RoleCommunicationProtocol=HTTPorHTTPS 11: ClientsUsePKICertificate=0 12: PrerequisiteComp=1 13: PrerequisitePath=\\test\ConfigMgrUpdates 14: AddServerLanguages=DEU 15: AddClientLanguages=DEU 16: MobileDeviceLanguage=0 17: ManagementPoint=test.osd.local 18: ManagementPointProtocol=HTTP 19: DistributionPoint=test.osd.local 20: DistributionPointProtocol=HTTP 21: DistributionPointInstallIIS=0 22: AdminConsole=1 23: 24: [SQLConfigOptions] 25: SQLServerName=test.osd.local 26: DatabaseName=CM_011 27: SQLSSBPort=4022 28: 29: [HierarchyExpansionOption] 30: CCARSiteServer=test0.osd.localI didn’t test this script, but I believe it should work, as I’ve already seen other articles around doing this.
- ‹ previous
- 16 of 25
- next ›
+++ Your opportunity +++ Use Profile Migrator 2, the new sepago product that makes migrating user personalities between different platforms a breeze.! Download your free version now!
Recent Articles
About the author
 |
David O'Brien IT-Consultant Blogs about VDI, App-DNA Apptitude, and deployment topics are my "thing" |
Add Comment