SCCM 2012 R2 with CAS

Hi
I have SCCM 2012 R2 CU4 (on Windows 2012 R2) with SQL 2012 (on Windows 2012 R2).
we decided to install a CAS,
there he has a procedure that
allows you to attach an existing SCCM
2012 R2 CAS?
Thanks

Assuming you've got a good reason to install a CAS, here is the procedure to expand a stand-alone primary site with a CAS:
https://technet.microsoft.com/en-us/library/jj591551.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Similar Messages

Reporting Service Error Code 7403, on SCCM 2012 R2 with SQL 2012 SP1 CU6

Dear All,
I am facing issue to install Reporting Services Point on SCCM 2012 R2 with SQL 2012 SP1 CU6. getting error messages id 7403. please let me know if SQL 2012 SP1 CU6 is supported with SCCM 2012 R2 or not & if you have any solution on it.
Error Message: The report server service is not running on Reporting Service Point server "SCCM2012"; start the service to enable reporting.

I am getting below error msg when trying to browse both sites
1) For Reports
The report server cannot decrypt the
symmetric key that is used to access sensitive or encrypted data in a report
server database. You must either restore a backup key or delete all encrypted
content. (rsReportServerDisabled)
Get Online Help
Keyset does not exist (Exception from
HRESULT:
0x80090016)
2) For Reportserver
Reporting Services Error
The report server cannot decrypt the symmetric key that is used to access
sensitive or encrypted data in a report server database. You must either restore
a backup key or delete all encrypted content. (rsReportServerDisabled)
Get Online Help
Keyset does not exist (Exception from HRESULT: 0x80090016)
SQL Server Reporting Services

Critical SMS_NOTIFICATION_SERVER ERROR sccm 2012 R2 WITH SQL 2012 SP1

Environement
SCCM 2012 R2
SQL 2012 SP1
On the same server
In sccm console i have in Monitoring - System Status - Component Status
critical SMS_NOTIFICATION_SERVER ERROR
Here are the two error that keep popping up
ERROR 1016
Site Component Manager failed to install this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart
Site Component Manager using the Configuration Manager Service Manager.
Folowing message
ERROR 4951
Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.
Here are the 2 logs
bgbsetuplog
<02/28/14 09:00:53> ====================================================================
<02/28/14 09:00:53> SMSBGB Setup Started....
<02/28/14 09:00:53> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:TCI-SCCMR2-LAV SMSBGB 0
<02/28/14 09:00:53> Installing Pre Reqs for SMSBGB
<02/28/14 09:00:53>         ======== Installing Pre Reqs for Role SMSBGB ========
<02/28/14 09:00:53> Found 1 Pre Reqs for Role SMSBGB
<02/28/14 09:00:53> Pre Req SqlNativeClient found.
<02/28/14 09:00:53> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<02/28/14 09:00:53> Pre Req SqlNativeClient is already installed. Skipping it.
<02/28/14 09:00:53>         ======== Completed Installation of Pre Reqs for Role SMSBGB ========
<02/28/14 09:00:53> Installing the SMSBGB
<02/28/14 09:00:53> Passed OS version check.
<02/28/14 09:00:53> IIS Service is installed.
<02/28/14 09:00:53> SMSBGB already installed (Product Code: {A78E8003-2307-4B70-B7CD-1A07C0A31D21}). Upgrading/Reinstalling SMSBGB
<02/28/14 09:00:53> New SMSBGB is the same product code. This is a minor upgrade.
<02/28/14 09:00:53> Enabling MSI logging. bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
<02/28/14 09:00:53> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration
Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<02/28/14 09:01:01> bgbisapi.msi exited with return code: 0
<02/28/14 09:01:01> Installation was successful.
<02/28/14 09:01:01> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /u "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<02/28/14 09:01:04> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/28/14 09:01:04> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<02/28/14 09:01:07> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/28/14 09:01:07> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
<02/28/14 09:01:07> Fatal MSI Error - bgbisapi.msi could not be install
bgpisapi.log
MSI (s) (00:60) [09:01:01:660]: Product: BGB http proxy -- Configuration completed successfully.
MSI (s) (00:60) [09:01:01:661]: Windows Installer reconfigured the product. Product Name: BGB http proxy. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
MSI (s) (00:60) [09:01:01:665]: Deferring clean up of packages/files, if any exist
MSI (s) (00:60) [09:01:01:665]: MainEngineThread is returning 0
MSI (s) (00:04) [09:01:01:670]: RESTART MANAGER: Session closed.
MSI (s) (00:04) [09:01:01:670]: No System Restore sequence number for this installation.
=== Logging stopped: 2/28/2014 9:01:01 ===
MSI (s) (00:04) [09:01:01:674]: User policy value 'DisableRollback' is 0
MSI (s) (00:04) [09:01:01:674]: Machine policy value 'DisableRollback' is 0
MSI (s) (00:04) [09:01:01:674]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:04) [09:01:01:675]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:04) [09:01:01:677]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (00:04) [09:01:01:678]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:04) [09:01:01:678]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (00:04) [09:01:01:679]: Destroying RemoteAPI object.
MSI (s) (00:B8) [09:01:01:679]: Custom Action Manager thread ending.
MSI (c) (3C:B8) [09:01:01:686]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (3C:B8) [09:01:01:686]: MainEngineThread is returning 0
MSI (c) (3C:B0) [09:01:01:690]: RESTART MANAGER: Session closed.
=== Verbose logging stopped: 2/28/2014 9:01:01 ===

Problem not fixed SORRY GUY'S
Environement
1 SERVER
WINDOWS SERVER 2012 R2
SQL SERVER 2012 SP1
SCCM 2012 R2
ERROR in system center
Message ID 1016
Site Component Manager failed to install this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart
Site Component Manager using the Configuration Manager Service Manager.
Message ID
4951
Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.
BGPSETUP.LOG
<03/05/14 09:49:33> ====================================================================
<03/05/14 09:49:33> SMSBGB Setup Started....
<03/05/14 09:49:33> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:TCI-SCCMR2-LAV SMSBGB 0
<03/05/14 09:49:33> Installing Pre Reqs for SMSBGB
<03/05/14 09:49:33>         ======== Installing Pre Reqs for Role SMSBGB ========
<03/05/14 09:49:33> Found 1 Pre Reqs for Role SMSBGB
<03/05/14 09:49:33> Pre Req SqlNativeClient found.
<03/05/14 09:49:33> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<03/05/14 09:49:33> Pre Req SqlNativeClient is already installed. Skipping it.
<03/05/14 09:49:33>         ======== Completed Installation of Pre Reqs for Role SMSBGB ========
<03/05/14 09:49:33> Installing the SMSBGB
<03/05/14 09:49:33> Passed OS version check.
<03/05/14 09:49:33> IIS Service is installed.
<03/05/14 09:49:33> SMSBGB already installed (Product Code: {A78E8003-2307-4B70-B7CD-1A07C0A31D21}). Upgrading/Reinstalling SMSBGB
<03/05/14 09:49:33> New SMSBGB is the same product code. This is a minor upgrade.
<03/05/14 09:49:33> Enabling MSI logging. bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
<03/05/14 09:49:33> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration
Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<03/05/14 09:49:41> bgbisapi.msi exited with return code: 0
<03/05/14 09:49:41> Installation was successful.
<03/05/14 09:49:41> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /u "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<03/05/14 09:49:43> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<03/05/14 09:49:43> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<03/05/14 09:49:45> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<03/05/14 09:49:45> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
<03/05/14 09:49:45> Fatal MSI Error - bgbisapi.msi could not be installed.
<03/05/14 09:49:45> ~RoleSetup().
BGBISAPI.LOG
=== Verbose logging started: 3/5/2014 9:49:33 Build type: SHIP UNICODE 5.00.9600.00 Calling process: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe ===
MSI (c) (08:C0) [09:49:33:974]: Resetting cached policy values
MSI (c) (08:C0) [09:49:33:974]: Machine policy value 'Debug' is 0
MSI (c) (08:C0) [09:49:33:974]: ******* RunEngine:
           ******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (08:C0) [09:49:33:974]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (08:C0) [09:49:33:974]: Grabbed execution mutex.
MSI (c) (08:C0) [09:49:34:021]: Cloaking enabled.
MSI (c) (08:C0) [09:49:34:021]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (08:C0) [09:49:34:025]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (C4:E4) [09:49:34:039]: Running installation inside multi-package transaction D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
MSI (s) (C4:E4) [09:49:34:039]: Grabbed execution mutex.
MSI (s) (C4:E8) [09:49:34:045]: Resetting cached policy values
MSI (s) (C4:E8) [09:49:34:045]: Machine policy value 'Debug' is 0
MSI (s) (C4:E8) [09:49:34:045]: ******* RunEngine:
           ******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
           ******* Action:
           ******* CommandLine: **********
MSI (s) (C4:E8) [09:49:34:047]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (C4:E8) [09:49:34:053]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (C4:E8) [09:49:34:057]: SRSetRestorePoint skipped for this transaction.
MSI (s) (C4:E8) [09:49:34:058]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (C4:E8) [09:49:34:060]: File will have security applied from OpCode.
MSI (s) (C4:E8) [09:49:34:065]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi' against software restriction policy
MSI (s) (C4:E8) [09:49:34:065]: SOFTWARE RESTRICTION POLICY: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi has a digital signature
MSI (s) (C4:E8) [09:49:34:067]: SOFTWARE RESTRICTION POLICY: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi is permitted to run because the user token authorizes execution (system or service token).
MSI (s) (C4:E8) [09:49:34:067]: MSCOREE not loaded loading copy from system32
MSI (s) (C4:E8) [09:49:34:077]: End dialog not enabled
MSI (s) (C4:E8) [09:49:34:077]: Original package ==> D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
MSI (s) (C4:E8) [09:49:34:077]: Package we're running from ==> C:\Windows\Installer\3897f9.msi
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (C4:E8) [09:49:34:081]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'.
MSI (s) (C4:E8) [09:49:34:081]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C4:E8) [09:49:34:094]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisablePatch' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (C4:E8) [09:49:34:095]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'.
MSI (s) (C4:E8) [09:49:34:095]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C4:E8) [09:49:34:096]: Transforms are not secure.
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log'.
MSI (s) (C4:E8) [09:49:34:096]: Command Line: REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR=D:\Program Files\SMS_CCM CCMSERVERDATAROOT=D:\Program Files\Microsoft Configuration Manager USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE
SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 CURRENTDIRECTORY=D:\Program Files\Microsoft Configuration Manager\bin\x64 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=5384
MSI (s) (C4:E8) [09:49:34:096]: Product Code passed to Engine.Initialize:           '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product Code from property table before transforms: '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product Code from property table after transforms: '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product registered: entering maintenance mode
MSI (s) (C4:E8) [09:49:34:096]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (C4:E8) [09:49:34:096]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is admin assigned: LocalSystem owns the publish key.
MSI (s) (C4:E8) [09:49:34:096]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is managed.
MSI (s) (C4:E8) [09:49:34:096]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:096]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (C4:E8) [09:49:34:096]: Specifed source is already in a list.
MSI (s) (C4:E8) [09:49:34:096]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (C4:E8) [09:49:34:096]: Machine policy value 'DisableBrowse' is 0
MSI (s) (C4:E8) [09:49:34:096]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (C4:E8) [09:49:34:096]: Adding new sources is allowed.
MSI (s) (C4:E8) [09:49:34:097]: Package name retrieved from configuration data: 'bgbisapi.msi'
MSI (s) (C4:E8) [09:49:34:099]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (C4:E8) [09:49:34:099]: Machine policy value 'DisableMsi' is 1
MSI (s) (C4:E8) [09:49:34:099]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (C4:E8) [09:49:34:099]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (C4:E8) [09:49:34:099]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is admin assigned: LocalSystem owns the publish key.
MSI (s) (C4:E8) [09:49:34:099]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is managed.
MSI (s) (C4:E8) [09:49:34:099]: Running product '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}' with elevated privileges: Product is assigned.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding REINSTALL property. Its value is 'ALL'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding REINSTALLMODE property. Its value is 'vmaus'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMINSTALLDIR property. Its value is 'D:\Program Files\SMS_CCM'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMSERVERDATAROOT property. Its value is 'D:\Program Files\Microsoft Configuration Manager'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSPORTS property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSPORTS property. Its value is '80'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSSSLPORTS property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSSSLPORTS property. Its value is '443'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSSSL property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSSSLSTATE property. Its value is '0'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMENABLELOGGING property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGLEVEL property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGMAXSIZE property. Its value is '1000000'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGMAXHISTORY property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'D:\Program Files\Microsoft Configuration Manager\bin\x64'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '5384'.
MSI (s) (C4:E8) [09:49:34:100]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '1ea81ab83bbb7c48a58c04b46f112051'.
MSI (s) (C4:E8) [09:49:34:104]: RESTART MANAGER: Session opened.
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:104]: TRANSFORMS property is now:
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '200'.
MSI (s) (C4:E8) [09:49:34:106]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming
MSI (s) (C4:E8) [09:49:34:106]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Favorites
MSI (s) (C4:E8) [09:49:34:108]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (s) (C4:E8) [09:49:34:109]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Documents
MSI (s) (C4:E8) [09:49:34:109]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (s) (C4:E8) [09:49:34:110]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Recent
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\SendTo
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Templates
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (s) (C4:E8) [09:49:34:112]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Local
MSI (s) (C4:E8) [09:49:34:114]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Pictures
MSI (s) (C4:E8) [09:49:34:124]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (C4:E8) [09:49:34:128]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (C4:E8) [09:49:34:129]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (s) (C4:E8) [09:49:34:131]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (s) (C4:E8) [09:49:34:132]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (s) (C4:E8) [09:49:34:135]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (C4:E8) [09:49:34:137]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (C4:E8) [09:49:34:138]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (s) (C4:E8) [09:49:34:139]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (s) (C4:E8) [09:49:34:141]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Desktop
MSI (s) (C4:E8) [09:49:34:144]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (s) (C4:E8) [09:49:34:144]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (s) (C4:E8) [09:49:34:144]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (C4:E8) [09:49:34:156]: MSI_LUA: Setting AdminUser property to 1 because the product is already installed managed and per-machine
MSI (s) (C4:E8) [09:49:34:156]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:156]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Windows User'.
MSI (s) (C4:E8) [09:49:34:156]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding Installed property. Its value is '00:00:00'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\3897f9.msi'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi'.
MSI (s) (C4:E8) [09:49:34:156]: Machine policy value 'MsiDisableEmbeddedUI' is 0
MSI (s) (C4:E8) [09:49:34:156]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
MSI (s) (C4:E8) [09:49:34:156]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
MSI (s) (C4:E8) [09:49:34:159]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (C4:E8) [09:49:34:159]: Machine policy value 'DisableRollback' is 0
MSI (s) (C4:E8) [09:49:34:159]: User policy value 'DisableRollback' is 0
MSI (s) (C4:E8) [09:49:34:159]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
MSI (s) (C4:E8) [09:49:34:159]: PROPERTY CHANGE: Adding QFEUpgrade property. Its value is '1'.
=== Logging started: 3/5/2014 9:49:34 ===
MSI (s) (C4:E8) [09:49:34:161]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (C4:E8) [09:49:34:161]: PROPERTY CHANGE: Adding Preselected property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:161]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
MSI (s) (C4:E8) [09:49:34:163]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (s) (C4:E8) [09:49:34:163]: Doing action: INSTALL
Action start 9:49:34: INSTALL.
MSI (s) (C4:E8) [09:49:34:165]: Running ExecuteSequence
MSI (s) (C4:E8) [09:49:34:165]: Doing action: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61
MSI (s) (C4:E8) [09:49:34:166]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
MSI (s) (C4:E8) [09:49:34:167]: PROPERTY CHANGE: Adding SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61 property. Its value is 'C:\Windows\SysWOW64\'.
Action start 9:49:34: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61.
MSI (s) (C4:E8) [09:49:34:167]: Doing action: System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61
Action ended 9:49:34: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61. Return value 1.
MSI (s) (C4:E8) [09:49:34:169]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
MSI

SCCM 2012 issue with HTTPS

Hello,
I have been trying to get a new SCCM 2012 environment running and I’ve hit a road block and hope someone can help.
I have installed SCCM 2012 SP1 w/ CU2 on a Windows 2012 server w/ MS SQL 2012.
When I installed SCCM I chose the PKI option and followed the instructions below to setup all the required certificates.
I have not yet installed any clients until I’ve verified everything is working correctly on the server.
PKI Setup Followed -> http://technet.microsoft.com/en-us/library/gg682023.aspx
The errors I’m seeing-
Both the Management Point and PORTALWEB are not responding to HTTP requests.
“The http status code and text is 401, Unauthorized.” I was chalking this up to how I have SCCM setup for HTTP only, but I could be wrong in thinking this.
If I navigate to either
https://<ServerName>/sms_mp/.sms_aut?mplist OR
https://<ServerName>/sms_mp/.sms_aut?mpcert I get the error “HTTP Error 403.7 – Forbidden”.
Below is a log grab from mpcontrol.log
SSL is enabled. SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Client authentication is also enabled.
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
CRL Checking is also enabled.     SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Machine name is 'SERVERNAME'.
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Begin validation of Certificate [Thumbprint xxxxb8aa] issued to 'SERVERNAME'
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Completed validation of Certificate [Thumbprint xxxxdb8aa] issued to 'SERVERNAME'
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Skipping this certificate which is not valid for ConfigMgr usage.
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM       5060 (0x13C4)
There are no certificate(s) that meet the criteria.
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM
5060 (0x13C4)
Performing machine FQDN to SAN2 search.
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Begin validation of Certificate [Thumbprint xxxx8196] issued to 'SERVERNAME'
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Certificate has "SSL Client Authentication" capability.
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM
5060 (0x13C4)
Completed validation of Certificate [Thumbprint xxxx8196] issued to 'SERVERNAME'
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Begin validation of Certificate [Thumbprint xxxx3324] issued to 'SERVERNAME'
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Certificate has "SSL Client Authentication" capability.
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM
5060 (0x13C4)
Completed validation of Certificate [Thumbprint xxxx3324] issued to 'SERVERNAME'
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Begin validation of Certificate [Thumbprint xxxxb8aa] issued to 'SERVERNAME'
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Completed validation of Certificate [Thumbprint xxxxb8aa] issued to 'SERVERNAME'
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Begin validation of Certificate [Thumbprint xxxx8bdf] issued to 'SERVERNAME'
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Certificate doesn't have "SSL Client Authentication" capabilities.
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Completed validation of Certificate [Thumbprint xxxx8bdf] issued to 'SERVERNAME'
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
>>> Selected Certificate [Thumbprint xxxx3324] issued to 'SERVERNAME' for HTTPS Client Authentication
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
Call to HttpSendRequestSync failed for port 443 with status code 403, text: Forbidden
SMS_MP_CONTROL_MANAGER
8/23/2013 12:37:00 PM 5060 (0x13C4)
NOTE – “Certificate [Thumbprint xxxx3324]” is the certificate binded to the Default Web Site as instructed in the PKI setup documentation.
What I have done-
Verified that the web and client certificates have the same and valid trusted root certificate.
Disabled CRL checking on web server.
If I modify the SSL Setting for SMS_MP in IIS to anything other than “Client Certificate: Required” then the 403 error goes away for the MPLIST and MPCERT checks and they are successful.
But this is changing the default setting and I am cautious to do this since it will decrease security.
Also I’m not sure where else would need to be changed and potentially breaking other functionality.
Any help on this would be greatly appreciated! Thank you

Hello,
I am still getting the error “HTTP Error 403.7 – Forbidden” when navigating to either
https://<ServerName>/sms_mp/.sms_aut?mplist OR
https://<ServerName>/sms_mp/.sms_aut?mpcert . In the IIS logs I see the below when I try the links above-
GET /sms_mp/.sms_aut mplist 443 - Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C;+.NET+CLR+3.5.30729;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.30729)
- 500 0 64 3
GET /sms_mp/.sms_aut mplist 443 - Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C;+.NET+CLR+3.5.30729;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.30729)
- 403 7 5 5
GET /sms_mp/.sms_aut mpcert 443 - Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C;+.NET+CLR+3.5.30729;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.30729)
- 500 0 64 1
GET /sms_mp/.sms_aut mpcert 443 - Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.2;+WOW64;+Trident/6.0;+.NET4.0E;+.NET4.0C;+.NET+CLR+3.5.30729;+.NET+CLR+2.0.50727;+.NET+CLR+3.0.30729)
- 403 7 5 29
Anyone else seen this issue? Have a possible resolution? Thanks!
When you use Internet Explorer to test out the Management Point, you will have to ensure that you have installed a
Client Authentication certificate into your Current User certificate store. When Internet Explorer is running under your user account, it will not search for certificates inside the
Local Computer certificate store.
Go ahead and enroll your user account in a Client Authentication certificate, and then try the request again. Internet Explorer will detect that a
Client Authentication certificate is required for the IIS website, and will prompt you to select the appropriate certificate to use for the request. See the screenshot below for an example.
After selecting the appropriate Client Authentication certificate, the request should succeed, and the XML response you are expecting will be displayed. In my screenshot below, the reason the certificate is not showing as "valid"
in Internet Explorer, is because it uses the Subject Name format that ConfigMgr requires for site system roles that are accessible from Internet
and Intranet.
Cheers,
Trevor Sullivan
Microsoft MVP: PowerShell
If this post was helpful, please click the little "Vote as Helpful" button :)
Trevor Sullivan
Trevor Sullivan's Tech Room
Twitter Profile

SCCM 2012 r2 with CU1 - XP Refresh

Hi Everyone,
Hoping someone out there can assist with this. I am doing a refresh for XP to win7. I have read
http://social.technet.microsoft.com/Forums/en-US/6e934990-999a-4367-860a-3ce4e5eda956/sccm-2012-r2-error-0x800700c1?forum=configmanagerosd
and
http://www.windows-noob.com/forums/index.php?/topic/9418-referesh-task-sequence-from-xp-fails-on-sccm-2012-r2/
none of these work. I took a look at this and I was able to get pass the staging of the boot image
http://blogs.technet.com/b/brandonlinton/archive/2013/06/21/how-to-create-and-import-a-winpe-3-1-boot-image-for-use-in-configmgr-2012-sp1-cu2.aspx
however when the machine rebooted I received this. I also inject the nic drivers using dism and still the same issue. Any idea of a fix or how to go about refresh for
XP using sccm 2012 r2?
thanks all!

Hi,
Also ran into this issue, you're encountering this error because some components are missing in your WinPE image.
Note that this refresh scenario is not supported, however you can get this to work by manually customizing (especially importing WMI component) your WinPE image
before importing it ConfigMgr.
I made the script below, ran in on a base WinPE image from WADK for Windows 8 (a 6.2 version image so) to make it work (sorry for french comments Inside but I'm sure you'll get it :) ):
#Adapt these variables to you environment
$ADK = "C:\Program Files (x86)\Windows Kits\8.0\Assessment and Deployment Kit" #Chemin d'ADK
$DismArchitecture = "amd64" #archi a utiliser pour DISM
$CompArchitecture = "x86" #archi a utiliser pour les composants
$MountDir = "e:\Mount" #point de montage a utiliser
$Wimdir = "E:\winpe.wim" #chemin du wim a modifier
$InjectDrivers = $TRUE #Choisir si il faut ajouter des pilotes ou non
$DriversDir = "E:\Pilotes\WinPE3.1_x86" #chemin contenant les pilotes
$AddCMTrace = $FALSE #Choisir si il faut ajouter cmtrace ou non
$CMTraceDir = "E:\Microsoft Configuration Manager\tools\cmtrace.exe" #chemin de cmtrace
$ChangeLocale = $TRUE #Choisir si il faut modifier les paramètre regionnaux ou non
$Locale = "fr-FR" #param regionnaux a utiliser
$DismFolder = "$ADK\Deployment Tools\$DismArchitecture\DISM" #ne pas modifier
$OptComponents = "$ADK\Windows Preinstallation Environment\$CompArchitecture\WinPE_OCs"; #ne pas modifier
$AddOPTComponents = $TRUE #Choisir si il faut ajouter des composants ou non
#liste des composants:
$ComponentList = @(
“$OptComponents\WinPE-WMI.cab”
“$OptComponents\$Locale\WinPE-WMI_$Locale.cab”
“$OptComponents\en-us\WinPE-WMI_en-us.cab”
“$OptComponents\WinPE-NetFx4.cab”
“$OptComponents\$Locale\WinPE-NetFx4_$Locale.cab”
“$OptComponents\en-us\WinPE-NetFx4_en-us.cab”
“$OptComponents\WinPE-HTA.cab”
“$OptComponents\$Locale\WinPE-HTA_$Locale.cab”
“$OptComponents\en-us\WinPE-HTA_en-us.cab”
“$OptComponents\WinPE-DismCmdlets.cab”
“$OptComponents\$Locale\WinPE-DismCmdlets_$Locale.cab”
“$OptComponents\en-us\WinPE-DismCmdlets_en-us.cab” );
#Composants pour WinPE 6.3: (a inserer a la place de NetFx4)
#“$OptComponents\WinPE-NetFx.cab”
#“$OptComponents\$Locale\WinPE-NetFx_$Locale.cab”
#“$OptComponents\en-us\WinPE-NetFx_en-us.cab”
#“$OptComponents\WinPE-PowerShell.cab”
#“$OptComponents\$Locale\WinPE-PowerShell_$Locale.cab”
#-----debut du script
#Creation du point de montage
New-Item -ItemType Directory -Force -Path $MountDir
#import de DISM
import-module $DismFolder
#montage de l'image
Write-Host "Mounting WIM file"
Mount-WindowsImage -ImagePath $Wimdir -Index 1 -Path $MountDir -ErrorAction Stop
#changement de locale
if($ChangeLocale -eq $TRUE)
Write-Host "Changing locale"
cd $DismFolder
dism.exe /image:$MountDir /set-syslocale:$Locale
dism.exe /image:$MountDir /set-userlocale:$Locale
dism.exe /image:$MountDir /set-inputlocale:$Locale
#ajout de cmtrace
if($AddCMTrace -eq $TRUE)
Write-Host "Adding CMTrace"
$CMTraceDest = $MountDir + "\Windows\System32"
Copy-Item -Path $CMTraceDir -Destination $CMTraceDest
#ajout des pilotes
if($InjectDrivers -eq $TRUE)
Write-Host "Injecting Drivers"
Add-WindowsDriver -Recurse -ForceUnsigned -Driver $DriversDir -Path $MountDir -Verbose -ErrorAction SilentlyContinue
#ajout des composants
if($AddOPTComponents -eq $TRUE)
Write-Host "Adding Optionnal Components"
foreach ($Component in $ComponentList)
Write-Host -Object (’Installing component: {0}’ -f $Component);
Add-WindowsPackage -Path $MountDir -PackagePath $Component -ErrorAction SilentlyContinue;
#demontage de l'image
Write-Host "Unmounting WIM file"
Dismount-WindowsImage -Path $MountDir -Save -Verbose
Mickael, My technet galleries contributions : ConfigMgr driver injector : http://gallery.technet.microsoft.com/ConfigMgr-Driver-Injector-aae7d17d SCCM Collection splitter : http://gallery.technet.microsoft.com/SCCM-Collection-Splitter-e1c82b06 ConfigMgr
TS Tools : http://gallery.technet.microsoft.com/TSTools-f9b01357

SCCM 2012 setup with local sql?

Hi,
During setup of SCCM 2012, you have the option
“Use a typical installation options for a Stand-alone primary site” This option will use only a local SQL server.
I wonder in what cases you would setup such a config. Probably for lab setups. It might be interesting for my lab config.
Can somebody tell me what the advantages/disadvantages of this config are (f.e. probably a sql express will be installed, will the sccm setup be fully functional)?
J.
Jan Hoedt

SQL express is not supported. That setting still assumes a local full SQL installation and it gives you all the default options. You shouldn't really use that option as you should customise your installation.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM 2012 report with BitLocker status

I am not an expert in SCCM 2012 Report Builder and i am trying to create a report with>
computername(laptop),drive letter, bitlocker status
I can't find the property to use in report builder to read the drive letter and bitlocker status. Is there someone who can help me out or had a rdl report file for me ?
PS. creating a query in SCCM 2012 is easy and works...but how to create a report out of it ??

SELECT dbo.v_R_System.Name0, dbo.v_GS_ENCRYPTABLE_VOLUME.DriveLetter0, dbo.v_GS_ENCRYPTABLE_VOLUME.ProtectionStatus0
FROM dbo.v_GS_ENCRYPTABLE_VOLUME INNER JOIN
dbo.v_R_System ON dbo.v_GS_ENCRYPTABLE_VOLUME.ResourceID = dbo.v_R_System.ResourceID
Please use the query above, you need to create your own data source of this Report. For more information, please ask at SQL forum, there is a dedicated SSRS forum for this kind of question.
Juke Chou
TechNet Community Support

SCCM 2012 integration with SCOM 2012 - Disable Alerts during patching

Have SCCM 2012 R2 and SCOM 2012 R2 and use the Software Update Patching process for servers. When using the checkbox to "Disable Operations Manager Alerts when this program runs" option have noticed on completion of the job and the target
server is rebooted, a scheduled task appears for a short time titled "SCOM 2007 Agent Resume Task". The task disappears and there is no history to view.
Is this a legacy naming convention from 2007 world when the maintenance mode is turned off from the SCCM patching process?
How do I see the actual code behind the SCCM and SCOM integration with Maintenance mode to validate it.

SCCM should use the following SCOM SDK to do that.
http://msdn.microsoft.com/en-us/library/bb437532.aspx
That's incorrect. There is no API or method to put an OpsMgr agent into maintenance mode on the client itself -- maintenance mode is a centrally controlled feature of OpsMgr. The API/code sample you linked is performing that activity on the management server
which assumes you know the management server name and have permissions to carry out the action -- neither of which is fulfilled by the ConfigMgr agent.
The ConfigMgr agent pauses the OpsMgr client agent service and also unloads the workflows from the OpsMgr agent (it only did the first part in ConfigMgr 2007). This effectively puts the agent in Maintenance Mode (although to my knowledge this is not directly
reflected in the OpsMgr console).
Jason | http://blog.configmgrftw.com

Connect via Windows Powershell in SCCM 2012 CONSOLE (with PowerShell 4.0 installed)

Hi,
When trying to "Connect via Windows Powershell" in the SCCM 2012 console, I get the message that Powershell 3.0 is not installed... (which actually isn't installed, we have PS4.0 installed). Do we need to install PS3.0 also to get it working
or is there a workaround? Connecting manually to the site via Powershell 4.0 (Get-Psdrive -psprovider CMSITE) works like a charm.
Regards,
WiM

Hi,
I have installed WMF 4.0 on Windows Server 2008 R2 sp1, it works fine.
Please try to use "$PSVersionTable" to confirm Powershell version is 4.0. At first, I forgot to install Microsoft .NET Framework 4.5, then the console gave me the message that Powershell 3.0 is not installed.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

SCCM 2012 R2 with PKI infrastructure

Hi,
Recently i have upgraded my SCCM 2012 R2 test lab from HTTP to HTTPS (PKI) Infrastruture.
I have all the things in place. Root CA has been defined and Native mode has been enabled in SCCM server. WEB server cert is in place, DP is also updated and assigned a certificate. Issued certificates to clients via Group policy.
Now my problem is, using task sequence i'm able to install operating system but Config Manager is unable to detect new client. Config manager client is installed on the system still SCCM server is not able to detect it, and if i check config manager client
properties, client certificate shows "None" value. Seems like clients are not communicating over HTTPS connection.
Please help.

Is there an auto enrollment policy set up in group policy for this device so it gets a PKI certificate?
http://sccmguy.com/2013/11/27/pki-certificates-for-configuration-manager-2012-r2-part-24-client-certificate-for-windows-computers/
Nash Pherson, Senior Systems Consultant
Now Micro -
My Blog Posts
If you found a bug or want the product to work differently,
share your feedback.
<-- If this post was helpful, please click the up arrow or propose as answer.

SCCM 2012 SP1 with remote WSUS on Server 2012 and SQL Server 2012

I am rebuilding my SCCM 2012 lab on Server 2012 R2 x64 OS now.
I have 1 primary site, remote SQL server 2012, and remote WSUS server.
Is the WSUS console still required on my primary site running server 2012? If so are the below the correct steps to get this working?
Install Console on primary server:
Go to Server Manager à Add Roles and features, Navigate to the features section.
Remote Server Manager tools
>Role Administration Tools
--Select Windows Server Update Services Tools Only
Are there any post hotfixes to install?
Intalling WSUS full version on remote server:
Go to Server Manager à Add Roles and features, Server Roles section.
Windows Server Update Services
Do I need to select this as well on the remote wsus server? >Role Administration Tools -Select Windows Server Update Services Tools Only
Since my SQL server is on a remote server do I select the below only?
Are there any post hotfixes to install?

Hi,
One Part of the question is already answered. The second part is: If you want to use a remote SQL Server you need to select exactly what you selected in your screenshot.
Regards,
Thomas
Thomas Hanrath [MCT | Regional Lead Germany] |
http://www.hanrath.de
Microsoft Learning Blog |
http://blog.microsoftlearning.de

Application uninstall bug of SCCM 2012 R2 with Cu2?

I install SCCM 2012 R2, then Update to CU1, last moth I had updated to CU2
I create two deployment type for winzip application.
It is 'available' and not 'required'.
Use script installer, it contains mst file. the script is vbs
One is for x64, the other is for x86. all of them contains uninstall program(msiexec /x {code} /q)
Install is ok
But the uninstall button is grayed out.
When I delete x86 deployment type then can uninstall this application
It seem if it has more than one of deployment type, the uninstall button is grayed out
I saw CU1 had fixed this bug, but why I met it again? It is new bug of SCCM 2012 R2 CU2?
I find R2 CU1 and R2 CU2 client update package in SCCM.
Do I need to deploy them to all PC?
If I use sccm OSD to install OS(Use default Configuration Manager Client Package）, If I need to update Client in this client？

Thanks, Narcoticoo & Torsten
I also do the test, it is because I didn't push the update to client, I have some new questions about Update CU
http://social.technet.microsoft.com/Forums/en-US/1b6161f4-2cdb-42a5-b59a-4b49970e2daf/how-to-update-cu1-cu2-to-sccm-2012-r2?forum=configmanagergeneral

Proper WSUS+SCUP on SCCM 2012 SP1 with SQL 2012

Been pulling my hair out a new build.
System:
Windows 2012
SQL 2012 SP1
WSUS 4.0
SCUP 2011
WSUS itself will synch if I set source= Microsoft Update.
SCCM SUP will synch with if I set source= Microsoft update.
SCUP will not connect to "update server" in this config.
SCUP will not connect if I check connect to local update server. Nor will it when i try to connect to itself as a remote (ie local host or fqdn in Update server screen)
Now whats weird is if I throw a proxy on my spare machine and aim WSUS and SCUP to use it try SUP to FQDNof SCCM host:8530....I can connect
The problem is with the proxy in play I cannot download Dell catalogs as it used FTP not HTTP (Adobe will download though)
Every so often just for fun it will throw "request for principal permission failed.
Anyone that has this working can you please tell me what you have on each of the SUp. WSUS and SCUP screens

Try running SCUP as administrator. This is usually necessary when SCUP is installed on the ConfigMgr/WSUS server and UAC is enabled. heres a guide that may help: http://www.youtube.com/watch?v=fyEGWSFWyy0 using Group Policy is the easiest wat to deploy
the certificates as well.
Justin Chalfant | Blog: setupconfigmgr.com | SCUP Catalog: patchmypc.net/scup | Please mark as helpful/answer if this resolved your issue

SCCM 2012 R2 With MDT 2012 AND MDT 2013 Side by Side

Currently we're running 2012 R2 CU3 with MDT 2012 integrated into it. We're looking at upgrading to MDT 2013 (whatever the latest update is). What I'm wondering, and can't seem to find any information on, is if we can continue to use our MDT 2012 boot
.wims/OSD Task Sequences/etc until such time as we create and test new ones or are we going to have to update everything right away?

Are you sure you are using MDT *2013* with ConfigMgr 2012 *R2*? That's not a supported configuration and I think there are multiple technical problems with this combination.
The task sequences themselves don't change -- because they are ConfigMgr task sequences -- but the MDT tasks must be updated to use the MDT 2013 tasks. Boot image use is partially dependent upon the OS you are deploying however only WinPE 3.1 and WinPE 5.0
based boot images are supported in R2.
Jason | http://blog.configmgrftw.com | @jasonsandys
Did you mean to ask if we were running MDT 2012 with ConfigMgr 2012 R2? Then yes we are. We did the upgrade from SP1 CU2 to R2 CU3 a couple of weeks ago but haven't upgraded MDT to 2013 yet. That's our next step but we also don't want to take down/break imaging
capability if we can help it (major college, staff/students constantly breaking stuff, etc).

SCCM 2012 OSD with Multiple Drive letters using StandAlone Media

Hey guys I have a client who is required to partition their Windows 8.1 installation in three different partitions:
C:(OS Partition)
d:(SQLData Partition)
E:(Client Data Partition)
G:(CD-ROM)
I Already know that I should not use multiple drives for OSD but this is the requirement I have been given...
When I deploy my TS through PxE or USB Bootable Media all the drives are labeled correctly... C,D and E but if I Use Standalone USB Media then I end up with C, E and F and G as CDRom. I know that WinPE assigns a drive letter to the usb stick usually d: but
not always so how can I set the USB Standalone media to act the same way as PxE and Usb Boot Media? is there a way to have PE set the USB drive to drives latter in the alphabet? s, t or w?
Please help

Hey Joyce thanks for the response but I am not talking about the fact that the drives are labeled differently in PE I am stating that once the imaging process is complete the drive letters are not the same when doing a deployment through PxE or USB Bootable
media... When using Full standalone USB media to deploy the exact same TS the drive letter assignment is not consistent so to be as clear as I can I will explain again...
When doing a deployment from PxE, USB BOOT Media or USB BOOT Media attached to a VM, all the drives end up correct at the end of the deployment so C: is the OS drive D: is the Data Drive and E: is the Maps Drive (Keep in mind that if I do a usb
bootable media deployment and leave the USB in the computer I have the same issue as the standalone media)
But if I run the deployment from a STANDALONE USB Media then everything runs as it should but when I enter windows and look at my drive letter assignment the C: is the OS drive the D: drive is the USB the E: drive is the Data drive and G: is the Maps
Drive...
Which means to me that when windows is assigning drive letters it is assigning the USB Drive as D and not something less intrusive like y: or o:
So the question is: How can I have the drive letters assigned properly when using full standalone media So that my deployments are consistent when deploying through PxE, Usb Boot Media and USB Standalone media? Did no one ever test this out? and if so is
this what I can expect from SCCM 2012R2 For consistency to not be available across all deployment methods?

SCCM 2012 R2 with CAS

Similar Messages

Maybe you are looking for