When Microsoft releases ConfigMgr 2012 R2 available on October 18th, along with all the other products, it will come with support for the following new platforms:
Site server and site system support will be added for the following operating systems:
Client support will be added for the following operating systems:
The Windows Assessment and Deployment Kit (Windows ADK) is a collection of tools that you can use to customize, assess, and deploy Windows operating systems to new computers.
Supported Operating System
To install the Windows ADK, your computer must be running one of the following operating systems:
• Windows 8.1
• Windows 8
• Windows 7
• Windows Server 2012 R2
• Windows Server 2012
• Windows Server 2008 R2
Direct Download Link: http://download.microsoft.com/download/6/A/E/6AEA92B0-A412-4622-983E-5B305D2EBE56/adk/adksetup.exe
A few facts about SEDO
When the UI crashes and causes locks, you can easily unlock or locate the Locks
run sql mangement studio against your DB
Show locks: select * from SEDO_LockState where LockStateID <> 0
Delete locks: delete from SEDO_LockState where id=’PLACE ID FROM ABOVE HERE’
This took me quite some time to figure out.
When running a build and capture task sequece from ConfigMgr, it won’t give any errors
Even after the image is captured and ready for re-deployment, the error appears when trying to run Setup Windows and Configmgr from a deployment task sequence. It would just break/stop right in the middel of that process, leaving your with pretty mush a useless deployment
Solution:
Set permission for group Administrators ( Full Control ) to
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepCleanup
Value Name
{EC9FE15D-99DD-4FB9-90D5-5B56E42A0F80}
Value Data
C:WindowsSysWOW64iesysprep.dll,Sysprep_Cleanup_IE
replace with
C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE
Set permission for group Administrators ( Full Control ) to
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepGeneralize
Value Name
{EC9FE15D-99DD-4FB9-90D5-CE53C91AB9A1}
Value Data
C:WindowsSysWOW64iesysprep.dll,Sysprep_Generalize_IE
replace with
C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE
Set permission for group Administrators ( Full Control ) to
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepSpecialize
Value Name
{EC9FE15D-99DD-4FB9-90D5-676C338DC1DA}
Value Data
C:WindowsSysWOW64iesysprep.dll,Sysprep_Cleanup_IE
replace with
C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE
setting this from a batch file:
IEhotfix.cmd:
regini -m \%computername% iesysprep.dll.txt reg add HKLMSOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepCleanup /v {EC9FE15D-99DD-4FB9-90D5-5B56E42A0F80} /t REG_SZ /d “C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE” /f reg add HKLMSOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepGeneralize /v {EC9FE15D-99DD-4FB9-90D5-CE53C91AB9A1} /t REG_SZ /d “C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE” /f reg add HKLMSOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepSpecialize /v {EC9FE15D-99DD-4FB9-90D5-676C338DC1DA} /t REG_SZ /d “C:WindowsSystem32iesysprep.dll,Sysprep_Cleanup_IE” /f
iesysprep.dll.txt
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepCleanup [1] HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepGeneralize [1] HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionSetupSysprepSpecialize [1]
System Center 2012 Configuration Manager R2 preview is available for download for MSDN subscribers.
System Center 2012 R2 Preview Configuration Manager (x86 and x64) – (Multilanguage).
http://msdn.microsoft.com/subscriptions/json/GetDownloadRequest?brand=MSDN&locale=en-us&fileId=53939&activexDisabled=false&akamaiDL=true
Ran into this issue when trying deploy an existing image – the image was created without the propertly OSDPreseveDriveLetter in the Build and Capture task sequence.
My deployment task sequence kept failing Setup Windows and Configmgr.
The CCM client installed on the system ended up broken
The error messages from ccmsetup.log
C:WINDOWSccmsetup{1AF71F68-6089-4211-ADDC-06DF40606141}client.msi installation failed. Error text: ExitCode: 1603
– Client installation has failed too many times. Ccmsetup will now abort.
Solution:
– Add OSDPreseveDriveLetter=False to Build and Capture Task sequecen
I really wanted to use the image that i already had created, so here is what i did:
1. Added the OSDPreseveDriveLetter=False in my deployment task sequecen
2. Added /forceinstall /SMSMP=FQDN /SMSSLP=FQDN to step Setup Windows and ConfigMgr
This is simple, but nice script to install the ConfigMgr Client – very handy in transition phases.
‘Install-CMClient.vbs
on error resume next
Dim currentVer
currentVer = “5.00.7711.0000”
‘Init common variables
Dim wshShell
Dim objFileSystem
Set wshShell = wscript.CreateObject(“wscript.Shell”)
Set objFileSystem = CreateObject(“scripting.FileSystemObject”)
‘Main Flow
If CheckSCCM = False Then
InstallSCCMAgent
ElseIf CheckSCCMVersion maxVer Then
maxVer = thisVer
End If
Next
CheckSCCMVersion = maxVer
End Function
It will be available from the System Center Eval Center:
http://technet.microsoft.com/en-us/evalcenter/hh505660.aspx or http://care.dlservice.microsoft.com/dl/download/3/4/C/34C7656A-F89E-473C-8CE0-21DA5DB0717C/configmgr_2012_RC2_ENU_7703.exe