Adding New SCCM 2012 SP1 Distribution Point To Replace Existing Distribution Point

We currently in the process of the doing a site server refresh at all our remote sites. Each remote site currently has a physical 2012 SP1 DP, and will be replaced with a new DP at each location, and will eventually decommission the current one.
What's the best way to introduce a new DP and remove the old one?
Thanks
Bern

You can use this method if distributing through the WAN is not an option.
http://blogs.technet.com/b/kensmith/archive/2013/08/01/migrating-the-content-library-between-distribution-points-in-sccm-2012-sp1.aspx
If you don't care, just add it to SCCM and replicate your content. Modify your boundary once done.
I hope you have a DP Group, if so, just make it member of the group and all your content will be copied. If not, you'll have to go through all your content and add it manually or script the process using PowerShell.
To remove your existing it's simply a matter of removing the "Distribution Point" role on your Server using the SCCM Console. (Administration / Site Configuration /Site Server, select your distribution point, right click Remove)
Benoit Lecours | Blog: System Center Dudes

Similar Messages

New SCCM 2012 client machines still getting SCCM 2012 SP1 client not the new SCCM 2012 SP1 CU3 client

Hi,
I've successfully (as far as I can tell) deployed SCCM 2012 SP1 CU3 and all my existing clients are showing a client version of 5.00.7804.1400. But when I setup a new client system recently I noticed that the client version was showing 5.00.7804.1000,
and not 5.00.7804.1400.
For new client systems, do I need to redeploy the packages that were created for SCCM 2012 SP1 CU3 so that the new systems get the new SCCM 2012 SP1 CU3 client?
Thanks,
Nick

Hi,
Here's some good information to look over:
http://sccmfaq.wordpress.com/2013/09/24/sccm-2012-include-cu-in-osd/
I haven't followed these instructions myself, since I haven't really had any good reason to include CUs during the initial installation process. I use this method instead and I've never run into any problems:
http://www.ronnipedersen.com/2013/06/installing-sccm-2012-sp1-cu2-quick-start-guide/
Don't retire TechNet! -
(Don't give up yet - 12,575+ strong and growing)

Management Point fails after installing SCCM 2012 SP1

I'm carrying out an install of SCCM 2012 SP1 with the following hardware (fresh install not an upgrade from 2007)
1. Newly built Windows Server 2012 box
2. Site database located on a remote SQL 2012 cluster, both nodes Windows Server 2012, with CU5
The install went fine but when checking the Site Server Components the Management Point isn't installing. The following both show errors;
SMS_MP_CONTROL_MANAGER - MP.msi could not install. Checked the MP.msi log file which shows the following errors;
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_Global.mof' (Phase: 3, Object: 5, Lines: 76 - 83, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\PolicyDefaults.mof' (Phase: 3, Object: 4, Lines: 49 - 57, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\StateMsgSchema.mof' (Phase: 3, Object: 6, Lines: 89 - 94, Error: 80041002)
[19:53:18] Failed to compile 'C:\Program Files\SMS_CCM\DataTransferService.mof' (Phase: 3, Object: 5, Lines: 318 - 323, Error: 80041002)
[19:53:19] Failed to compile 'C:\Program Files\SMS_CCM\CcmExec_MP.mof' (Phase: 3, Object: 1, Lines: 31 - 36, Error: 80041002)
MSI (s) (0C!94) [19:53:20:862]: Product: ConfigMgr Management Point -- Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
Error 25140. Setup was unable to compile the file CcmExec_Global.mof
The error code is 80041002
CustomAction CcmRegisterWmiMofFile returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
SMS_NOTIFICATION_SERVER - bgbisapi.msi could not install. Extract from log below;
[19:53:38] IGNORE: Failed to delete extension 'C:\Program Files\SMS_CCM\bgbisapi.dll'. Return Code = 0x80020009 (The extension might not be registered)
[19:53:39] WARNING: Failed to remove PerfLib entries for performance application SmsBgb (2)
[19:53:39] WARNING: Failed to remove configuration for performance application SmsBgb (80070057)
MSI (s) (0C!80) [19:53:39:540]: Product: BGB http proxy -- Internal Error 25001. 80070057
Internal Error 25001. 80070057
CustomAction CcmRegisterPerfCounters returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
I've tried uninstalling MP and reinstalling, triple checked all the right pre-reqs in Roles and Features are enabled, even rebuilt the server from scratch and tried again but same result.
Would really appreciate some help if anyone's fixed this issue

I'm still struggling, I've uninstalled MP
<04/16/14 08:06:59> SMSMP Setup Started....
<04/16/14 08:06:59> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /deinstall /siteserver:EICSC001 SMSMP 0
<04/16/14 08:06:59> Deinstalling the SMSMP
<04/16/14 08:06:59> No versions of SMSMP are installed. Returning Success.
<04/16/14 08:06:59> ~RoleSetup().
Ran the command, Invoke-Command {gwmi -query "SELECT * FROM __Namespace WHERE Name='CCM'" -Namespace "root" | Remove-WmiObject}
Checked Namespace Instances to ensure '= ccm' is not longer there.
Rebooted Server and re-installed MP but it still fails
<04/16/14 08:37:26> ====================================================================
<04/16/14 08:37:26> SMSMP Setup Started....
<04/16/14 08:37:26> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:EICSC001 SMSMP 0
<04/16/14 08:37:26> Installing Pre Reqs for SMSMP
<04/16/14 08:37:26> ======== Installing Pre Reqs for Role SMSMP ========
<04/16/14 08:37:26> Found 2 Pre Reqs for Role SMSMP
<04/16/14 08:37:26> Pre Req MSXML60 found.
<04/16/14 08:37:26> No versions of MSXML60 are installed. Would install new MSXML60.
<04/16/14 08:37:26> Enabling MSI logging. msxml6_x64.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log
<04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi
<04/16/14 08:37:26> msxml6_x64.msi exited with return code: 0
<04/16/14 08:37:26> msxml6_x64.msi Installation was successful.
<04/16/14 08:37:26> Pre Req SqlNativeClient found.
<04/16/14 08:37:26> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<04/16/14 08:37:26> Pre Req SqlNativeClient is already installed. Skipping it.
<04/16/14 08:37:26> ======== Completed Installation of Pre Reqs for Role SMSMP ========
<04/16/14 08:37:26> Installing the SMSMP
<04/16/14 08:37:26> Passed OS version check.
<04/16/14 08:37:26> IIS Service is installed.
<04/16/14 08:37:26> No versions of SMSMP are installed. Installing new SMSMP.
<04/16/14 08:37:26> Enabling MSI logging. mp.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log
<04/16/14 08:37:26> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\mp.msi 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
<04/16/14 08:37:26> mp.msi exited with return code: 1603
<04/16/14 08:37:26> Backing up D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log to D:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<04/16/14 08:37:26> Fatal MSI Error - mp.msi could not be installed.
<04/16/14 08:37:26> ~RoleSetup().
On checking I don't seem to have anything in IIS, no default web site.
I've tried reinstalling IIS and reinstalling SCCM 2012 but what ever I do I still hit the same issue with the Management Point.
Any assistance would be greatly appreciated.
Thanks

Windows 8.1 system with new Office 2013 install not pulling down any Office 2013 updates from my SCCM 2012 SP1 server

Hi,
I've just setup a new Windows 8.1 system and added to my SCCM 2012 SP1 server and all is good and it pulled down all the correct Windows updates and pulls down automatically the FEP updates that are distributed from SCCM 2012 daily.
I just installed Office 2013 on this system and have activated it as necessary. The problem is that the system doesn't seem to be pulling down any of the Office 2013 updates that have distributed thru SCCM. I have other systems with
Office 2013 installed and they have pulled down Office 2013 updates in the past when I published them.
If I look at the Office 2013 updates in the SCCM console software section, I can see that for example it shows that Office 2013 SP1 (x86) is needed by one system and installed on 8 other systems and shows as downloaded and deployed.
I've restarted the new system multiple times and also tried to force a software update check from the Configuration Manager applet but nothing seems to happen.
What can I check to try and determine what the problem is?
Thanks in advance,
Nick

Yes, the 8.1 system is a member of collection where the update deployment is targeted.
Are there any specific logs I should check in the client? If I check the WindowsUpdate.log I can see messages about the machine pulling down the FEP updates but that's all it appears to be doing.
in CCM\logs, focus on the updatehandler and updatedeployment, to begin with
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

SCCM 2012 SP1 WSUS/Software Update Point Synchronization error on CAS.

Hi All,
Good day to all you.
I would like to seek all your help on this issue that i have encountering.
My SCCM 2012 SP1 CAS are having a synchronization error in WSUS/Software update point. The CAS have intergrated WSUS role in it. The last good synchronization was on July 16, 2014. No error log found on WCM.log and WSUSctrl.log
Error:
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall).
Source: Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM 5776 (0x1690)
Sync failed. Will retry in 60 minutes
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
below are wsyncmgr.log:
Setting sync alert to active state on site C01 SMS_WSUS_SYNC_MANAGER (0x1690)
Sync time: 0d00h01m14s SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Wakeup for a polling cycle SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Starting Sync SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Performing sync on retry schedule SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Read SUPs from SCF for MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Found 1 SUPs SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
Found active SUP MYHQKUL990707S.sdb.com from SCF File.
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:20.750 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:20 PM
5776 (0x1690)
Synchronizing WSUS server MYHQKUL990707S.sdb.com SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
STATMSG: ID=6704 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:04:21.763 2014 ISTR0="" ISTR1="" ISTR2="" ISTR3=""
ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:04:21 PM
5776 (0x1690)
Using account sdb\SCCM-Admin to connect to WSUS Server
SMS_WSUS_SYNC_MANAGER 5776 (0x1690)
Synchronizing WSUS server myhqkul990707s.sdb.com ...
SMS_WSUS_SYNC_MANAGER 440 (0x01B8)
sync: Starting WSUS synchronization SMS_WSUS_SYNC_MANAGER
440 (0x01B8)
Sync failed: UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall). Source:
Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=MYHQKUL990707S.sdb.com SITE=C01 PID=6948 TID=5776 GMTDATE=Tue Jul 22 07:05:32.796 2014 ISTR0="Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncWSUS"
ISTR1="UssNotFound: WebException: The request failed with HTTP status 404: Not Found.~~at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_WSUS_SYNC_MANAGER 7/22/2014 3:05:32 PM
5776 (0x1690)
Sync failed. Will retry in 60 minutes SMS_WSUS_SYNC_MANAGER
5776 (0x1690)
All response is much appreciated
Thank You

Hi,
I recommend you look at the IIS log. Maybe it can give us some clues.
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.

[Forum FAQ] Management Point fails after installing SCCM 2012 SP1

Symptom:
The Management Point might fail to be installed after you install SCCM 2012 sp1 on Windows Server 2012, either fresh install or others.
You might see some errors in mpMSI.log like listed below.
“Setup was unable to compile the file CcmExec_Global.mof”
“The error code is 80041002”
Cause:
Reinstall Management Point cannot work. This is because CCM Namespace remains in WMI which prevents SCCM from installing MP. You need clear CCM Namespace from WMI.
Resolution:
1. Uninstall Management Point from the console, then wait for the uninstallation to finish in MPSetup.log.
2. Open Wbemtest -> Connect to root -> Click Enum Classes and choose Recursive -> Double click _NAMESPACE in Query Result dialog -> Click Instances -> Delete _NAMESPACE.Name=”ccm”
3. Install Management Point.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Symptom:
The Management Point might fail to be installed after you install SCCM 2012 sp1 on Windows Server 2012, either fresh install or others.
You might see some errors in mpMSI.log like listed below.
“Setup was unable to compile the file CcmExec_Global.mof”
“The error code is 80041002”
Cause:
Reinstall Management Point cannot work. This is because CCM Namespace remains in WMI which prevents SCCM from installing MP. You need clear CCM Namespace from WMI.
Resolution:
1. Uninstall Management Point from the console, then wait for the uninstallation to finish in MPSetup.log.
2. Open Wbemtest -> Connect to root -> Click Enum Classes and choose Recursive -> Double click _NAMESPACE in Query Result dialog -> Click Instances -> Delete _NAMESPACE.Name=”ccm”
3. Install Management Point.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Migration of SCCM 2012 SP1 to SCCM 2012 R2 in a new domain.

I am wondering if it is possible to migrate objects from a SCCM 2012 SP1 server in one domain to a new SCCM 2012 R2 server in another domain ?
I read this article, but it does not state this particular combination.
http://technet.microsoft.com/en-us/library/gg682006.aspx
Thx
Thomas

For Migrate from SCCM 2012 SP1 to SCCM 2012 R2 in same environment/Domain, it's support and applicable.
But migrate to new domain, it's not support. Also you can't migrate database for new domain or object. you will need to rebuild it.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

SCCM 2012 SP1 MDT task sequence fails on reboot does not retain ip

we are having a sccm 2012 sp1 server that used for installation of win 8.1 Enterprise , the task sequence works perfectly fine but when we run the same task on HP Elite 8300 system having Intel 82579LM Adapter from Windows XP , after the reboot the
task fails as no ip address is assigned the NIC , We did download the WInPE Adapter drivers from HP site and injecting to the x86 Boot Image (6.2.9200) however the task still fails ,
Our environment uses all static ip address , the same task as mentioned earlier has worked fine with Different brands of HP elite 8200/8100 , infact the elite 8200 also uses the same NIC card
Find below the smsts.log file
Main error in the log file is
No physical network adapters found   OSDNetSettings   2/12/2014 1:02:38 AM   2064 (0x0810)
Found network adapter "Intel(R) 82579LM Gigabit Network Connection" with IP Address 169.254.181.151.   TSMBootstrap   2/12/2014 1:05:41 PM   1984 (0x07C0)
Xtract from LOG
SMSTSRebootDelay=60   Reboot   2/12/2014 1:01:56 AM   3496 (0x0DA8)
SMSTSRebootMessage=A new Microsoft Windows operating system is being installed. The computer must restart to continue.   Reboot   2/12/2014 1:01:56 AM   3496 (0x0DA8)
SMSTSRebootRequested=WinPE   Reboot   2/12/2014 1:01:56 AM   3496 (0x0DA8)
Process completed with exit code 0   TSManager   2/12/2014 1:01:56 AM   1876 (0x0754)
!--------------------------------------------------------------------------------------------!   TSManager   2/12/2014 1:01:56 AM   1876 (0x0754)
Successfully completed the action (Restart to Windows PE) with the exit win32 code 0   TSManager   2/12/2014 1:01:56 AM   1876 (0x0754)
Set authenticator in transport   TSManager   2/12/2014 1:01:56 AM   1876 (0x0754)
Set a global environment variable _SMSTSLastActionRetCode=0   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Set a global environment variable _SMSTSLastActionSucceeded=true   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Clear local default environment   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Updated security on object E:\_SMSTaskSequence.   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Save the current environment block   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Executing command line: "bcdedit.exe"   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
CreateProcess failed. Code(0x80070002)   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Command line execution failed (80070002)   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
Staging boot image UNB0003A   TSManager   2/12/2014 1:01:57 AM   1876 (0x0754)
ResolveSource flags: 0x00000000   TSManager   2/12/2014 1:01:59 AM   1876 (0x0754)
SMSTSPersistContent: . The content for package UNB0003A will be persisted   TSManager   2/12/2014 1:01:59 AM   1876 (0x0754)
Set authenticator in transport   TSManager   2/12/2014 1:01:59 AM   1876 (0x0754)
WinHttp credentials set   TSManager   2/12/2014 1:01:59 AM   1876 (0x0754)
List of files to be downloaded   TSManager   2/12/2014 1:01:59 AM   1876 (0x0754)
Downloaded file from http://unb-ho-sccmdb.exch1.mas.unb.com:80/SMS_DP_SMSPKG$/UNB0003A/sccm?/WinPE.UNB0003A.wim to E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim    TSManager   2/12/2014 1:02:22 AM   1876
(0x0754)
VerifyContentHash: Hash algorithm is 32780   TSManager   2/12/2014 1:02:22 AM   1876 (0x0754)
Found boot image E:\_SMSTaskSequence\Packages\UNB0003A\WinPE.UNB0003A.wim   TSManager   2/12/2014 1:02:25 AM   1876 (0x0754)
Copying boot image locally...   TSManager   2/12/2014 1:02:25 AM   1876 (0x0754)
Failed to find ADK installation root registry key   TSManager   2/12/2014 1:02:32 AM   1876 (0x0754)
Opening image file E:\_SMSTaskSequence\WinPE\sources\boot.wim   TSManager   2/12/2014 1:02:32 AM   1876 (0x0754)
Applying image 1 to volume E:\_SMSTaskSequence\WinPE   TSManager   2/12/2014 1:02:32 AM   1876 (0x0754)
Closing image file E:\_SMSTaskSequence\WinPE\sources\boot.wim   TSManager   2/12/2014 1:02:35 AM   1876 (0x0754)
Capturing WinPE bootstrap settings   TSManager   2/12/2014 1:02:35 AM   1876 (0x0754)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}   TSManager   2/12/2014 1:02:35 AM   1876 (0x0754)
Executing command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}   TSManager   2/12/2014 1:02:35 AM   1876 (0x0754)
==============================[ OSDNetSettings.exe ]===========================   OSDNetSettings   2/12/2014 1:02:36 AM   2064 (0x0810)
Command line: "osdnetsettings.exe" capture adapters:true scope:Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}   OSDNetSettings   2/12/2014 1:02:36 AM   2064 (0x0810)
No adapters found with non-empty DNSDomainSuffixSearchOrder   OSDNetSettings   2/12/2014 1:02:36 AM   2064 (0x0810)
Adapter "ROOT\SYMC_TEEFER2MP\0000" not found   OSDNetSettings   2/12/2014 1:02:38 AM   2064 (0x0810)
No physical network adapters found   OSDNetSettings   2/12/2014 1:02:38 AM   2064 (0x0810)
OSDNetSettings finished: 0x00000000   OSDNetSettings   2/12/2014 1:02:38 AM   2064 (0x0810)
Process completed with exit code 0   TSManager   2/12/2014 1:02:38 AM   1876 (0x0754)
Installing boot image to hard drive   TSManager   2/12/2014 1:02:38 AM   1876 (0x0754)
Backing up existing boot system before trying to set up new boot system   TSManager   2/12/2014 1:02:38 AM   1876 (0x0754)
BootLoader::backup: C:\, E:\_SMSTaskSequence\backup   TSManager   2/12/2014 1:02:39 AM   1876 (0x0754)
BootLoader::restore: E:\_SMSTaskSequence\WinPE, C:\   TSManager   2/12/2014 1:02:43 AM   1876 (0x0754)
Saving bcd store to E:\_SMSTaskSequence\WinPE\boot\BCD   TSManager   2/12/2014 1:02:43 AM   1876 (0x0754)
Executing command line: "E:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe" /NT60 SYS /MBR   TSManager   2/12/2014 1:02:45 AM   1876 (0x0754)
Process completed with exit code 0   TSManager   2/12/2014 1:02:46 AM   1876 (0x0754)
Updated security on object E:\_SMSTaskSequence.   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Save the current environment block   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Updated security on object D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Updated security on object E:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca.   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Updated security on object E:\_SMSTaskSequence.   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a global environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSNextInstructionPointer=59   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a global environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Set a TS execution environment variable _SMSTSInstructionStackString=0 41 57   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Save the current environment block   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
Expand a string: %_SMSTSMDataPath%\Logs   TSManager   2/12/2014 1:02:47 AM   1876 (0x0754)
<![LOG[LOGGING: Finalize process ID set to 780]LOG]!><time="01:04:01.537+480" date="02-12-2014" component="TSBootShell" context="" type="1" thread="784" file="tslogging.cpp:1495">
   1/1/1601 12:00:00 AM   1995266923 (0x76ED5B6B)
==============================[ TSBootShell.exe ]==============================   TSBootShell   2/12/2014 1:04:01 AM   784 (0x0310)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'   TSBootShell   2/12/2014 1:04:01 AM   784 (0x0310)
Debug shell is enabled   TSBootShell   2/12/2014 1:04:01 AM   784 (0x0310)
Waiting for PNP initialization...   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(3)\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
WinPE boot path: E:\_SMSTASKSEQUENCE\WINPE\SOURCES\BOOT.WIM   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
Booted from fixed disk   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
Found config path E:\_SMSTaskSequence   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,549)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
Restoring boot system from E:\_SMSTaskSequence\backup   TSBootShell   2/12/2014 1:04:01 AM   796 (0x031C)
Successfully loaded the BCD boot system   TSBootShell   2/12/2014 1:04:05 AM   796 (0x031C)
Successfully loaded an exported NTLDR boot system   TSBootShell   2/12/2014 1:04:05 AM   796 (0x031C)
BootLoader::restore: E:\_SMSTaskSequence\backup, C:\   TSBootShell   2/12/2014 1:04:05 AM   796 (0x031C)
Successfully merged logs from cache.   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,515)   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,337)   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,430)   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Loading bootstrap settings from E:\_SMSTaskSequence\WinPE   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Loading saved WinPE settings   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00450037004500350042004200360039002D0036003100390038002D0034003500350035002D0042003500430041002D003600430034003600410032004200350045004200370038007D00'   TSBootShell
2/12/2014 1:04:06 AM   796 (0x031C)
Environment scope successfully created: Global\{E7E5BB69-6198-4555-B5CA-6C46A2B5EB78}   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Configuring WinPE bootstrap settings   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Creating WinPE answer file   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Setting hive location to "X:\windows\system32"   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Getting namespace "Microsoft-Windows-Setup" for architecture "x86"   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Configuring global network settings   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Join type:    TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
DNS domain: exch1.mas.unb.com   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
DNS domain search order:    TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
IP filter sec enabled: false   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
No adapters found in environment. Performing global configuration only.   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Writing configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Successfully saved configuration information to E:\_SMSTaskSequence\WinPE\WinPeUnattend.xml   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
Executing command line: wpeinit.exe -winpe   TSBootShell   2/12/2014 1:04:06 AM   796 (0x031C)
The command completed successfully.   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
Starting DNS client service.   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
Finalizing network settings   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
No adapters found in environment. Performing global finalization only.   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
Finalizing global network settings   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
DNS domain: exch1.mas.unb.com   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
DNS domain search order:    TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
DNS for WINS enabled: false   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
LMHosts file enabled: true   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
Host lookup file:    TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
WINS scope ID:    TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
The command completed successfully.   TSBootShell   2/12/2014 1:05:40 AM   796 (0x031C)
==============================[ TSMBootStrap.exe ]==============================   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:E:\_SMSTaskSequence   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL'   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Adding SMS bin folder "X:\sms\bin\i386" to the system environment PATH   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Failed to open PXE registry key. Not a PXE boot.   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Resuming Task Sequence in WinPE   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'   TSMBootstrap
2/12/2014 1:05:40 AM   1984 (0x07C0)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'   TSMBootstrap
2/12/2014 1:05:40 AM   1984 (0x07C0)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}   TSMBootstrap   2/12/2014 1:05:40 AM   1984 (0x07C0)
Loading the Task Sequencing Environment from "E:\_SMSTaskSequence\TSEnv.dat".   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Updating the local data path in the Task Sequencing Environment.   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Setting LogMaxSize to 1000000   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Setting LogMaxHistory to 1   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Setting LogLevel to 0   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Setting LogEnabled to 1   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Setting LogDebug to 1   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Command line for extension .exe is "%1" %*   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Set command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
Executing command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:WinPE   TSMBootstrap   2/12/2014 1:05:41 AM   1984 (0x07C0)
==========[ TsProgressUI started in process 2004 ]==========   TsProgressUI   2/12/2014 1:05:41 AM   2008 (0x07D8)
Command line: "X:\sms\bin\i386\TsProgressUI.exe" /Register:W
In dire need of help,
I have already gone through the below articles on the NET
http://social.technet.microsoft.com/Forums/systemcenter/en-US/0fe5cded-51cf-487a-97e3-837fb3426a3e/install-software-updates-in-osd-reboots-leaves-clients-in-provisioning-mode?forum=configmgrosd
http://social.technet.microsoft.com/Forums/systemcenter/en-US/c590e486-d3ca-423f-8953-e596160f3567/updates-hang-during-osd-kb2509007-not-working-for-me?forum=configmgrosd
Awating response,
Hasan Reza

Well Finally I sorted my issue ,
Just want to share the solution, may be it would be helpful to some one else and save some times
The problem was that the Xp images has lot of hidden NIC installed , this would not allow the system to work with the correct NIC card and Ip address (System -> View Hidden Devices) , what I did 2 things
1) Copied the OSD Script folder from the SCCM Server to the Client pc and ran that ztigather.wsf and captured the output , it was evident that it showed capturing multiple adapters , (There are some blogs that pointed out that OSD can capture only one nic
due to the only one Adapter0 section being defined in the ZTIgather.xml file,)
2) I open the registry at the xp pc navigated to HKLM-> System ->Current Control Set-> Services-> TCPIP -> Parameters-> Interfaces ->
Expect for the NIC card that had the Ip address assigned I deleted all other nic card's guid,
As then post running deleting the old scanstate (USMTUTIL /rd c:\statestore) , reran the task and VOILA..
All worked fine , below are the two post I followed , though notvery relevant but they were helpful and help me reached the conclusion.
Thanks,
Hasan Reza.
http://systemscenter.ru/mdt2012.en/ztigatherwsf.htm
http://social.technet.microsoft.com/Forums/windowsserver/en-US/8acb7cd1-7028-4ffe-86c9-eb43041cf8b3/how-do-i-get-rid-of-second-169254xx-ipv4-address-on-windows-server-2008-sp2-x86?forum=winservergen

Deploy Windows 8 To Go through SCCM 2012 SP1

First a little backgroud:
I have SCCM 2012 SP1 with MDT 2012 Update 1 integrated. I am using an MDT UDI task sequence to deploy windows 8 and it works perfectly. My Windows 8 image is fairly thin (only containing OS updates and C++ runtimes), and I am using the MDT database
and an MDT task sequence in SCCM 2012 to dynamically set a list of SCCM Applications to install as well as settings based on location.
Now I want to get Windows To Go provisioning working in SCCM 2012 SP1. I had a powershell script that preparied the drive and applied a thick image (including office and other apps) to it then updated unattend.xml with a computer name and the domain join
info. That worked for me however I'd like to levarage the dynamic task sequence that I described above to build these To Go sticks the same as my other Windows 8 machines without having to keep updating the thick image evertime something changes.
There isn't much info out there that Iv'e found on setting up SCCM 2012 SP1 to provision windows to go here are the two that I have found
http://ixrv.blogspot.com/2012/10/provisioning-windows-8-to-go-with.html
http://technet.microsoft.com/en-us/library/jj651035.aspx
I followed the instructions in the first link and was able to run the Windows to Go Creator program and apply the prestaged wim to the USB stick. I rebooted from the USB stick Windows PE started and started to run my task sequence then it errored out on
the apply image step. At this point it occured to me that the MDT SCCM task sequence was probably not setup for prestaged media and or Windows To Go.
So my question is am I on the right track? Do I just need to examine each step in my task sequence and make sure that it will work properly with my Prestaged/Windows To Go stick? If so has anyone actually gotten this to work that could give me some advice?
Or is it asking too much to have a dynamic Windows To Go task sequence and I should just be building a thick image and using a second task sequence specifically for Windows to go?
are there any other resources for Windows To Go with SCCM that I'm missing?
Thanks,
Tony

First of all sorry I missed your last three posts I have to check my email notifications. I'll try to answer all of them even though I think the last part is the only one where you are still stuck.
When I created my prestaged media I didn't put anything into it except for the the OS image and my PE image. On the Select Application and Select Package screen in the prestaged media wizard remove any application or packages that are added automatically.
The task sequence is supposed to be smart enough to know if the version of the package that is on the prestaged media is out of date and go to a DP to get it but that didnt work for me. The only way I was able to get it to work was to remove all the packages
from the prestaged media even the Customsettings package, the MDT toolkit package, USMT, etc..
http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/d729d0ff-829f-4af8-91af-2131b3355fd0/
This thread which is about prestaged media in SCCM 2007 helped me to understand how prestaged media is supposed to work. Basically what I learned is that once the computer is rebooted from the ToGo stick into PE the task sequence will run the same as any
other task sequence installing any applications and setting up your ToGo stick just like any other computer that runs the task sequence they dont need to be in your prestaged media for this to happen.
You shouldn't need to worry about partitioning WTGCreator.exe will partition the ToGo stick for you I'm just using the standard MDT Integrated partitioning in my task sequence. The one thing that I did was set the Windows To Go Creator package to "run from
distribution point" which speed things up because then it didnt download the prestaged wim then apply it to the USB drive.
Is it booting into PE then rebooting? Did you check the "Allow unattend operating system deployment" check box when you made your prestaged media? If so it wants you to have set the task sequence to run in a task sequence variable SMSTSPreferredAdvertID
to the task sequence ID you want to run. I'd just remake the media and leave that box unchecked.
Good luck and let me know how it works for you. I'll check back sooner this time I promise.

DP Job queue manager not working- SCCM 2012 SP1

I am getting below error when trying to open DP job queue manager in sccm 2012 SP1
Please find the details information
see the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException:
Invalid query
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
   --- End of inner exception stack trace ---
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
   at DPJobMgr.Form1.SummaryRefresh_Click_real(Object sender, EventArgs e)
   at DPJobMgr.Form1.SummaryRefresh_Click(Object sender, EventArgs e)
   at System.Windows.Forms.TabControl.OnSelectedIndexChanged(EventArgs e)
   at System.Windows.Forms.TabControl.WmSelChange()
   at System.Windows.Forms.TabControl.WndProc(Message&
m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd,
Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1008 (RTMGDR.030319-1000)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
DPJobMgr
    Assembly Version: 5.0.0.0
    Win32 Version: 5.0.7958.1000
    CodeBase: file:///C:/Program%20Files%20(x86)/ConfigMgr%202012%20Toolkit%20R2/ServerTools/DPJobMgr.exe
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1002 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1001 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1001 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
Microsoft.ConfigurationManagement.ManagementProvider
    Assembly Version: 5.0.0.0
    Win32 Version: 5.0.7958.1000
    CodeBase: file:///C:/Program%20Files%20(x86)/ConfigMgr%202012%20Toolkit%20R2/ServerTools/Microsoft.ConfigurationManagement.ManagementProvider.DLL
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
System.Data.Linq
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1015
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Data.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Data.Linq.dll
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 (RTMRel.030319-0100)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
AdminUI.WqlQueryEngine
    Assembly Version: 5.0.0.0
    Win32 Version: 5.0.7958.1000
    CodeBase: file:///C:/Program%20Files%20(x86)/ConfigMgr%202012%20Toolkit%20R2/ServerTools/AdminUI.WqlQueryEngine.DLL
System.Configuration
    Assembly Version: 4.0.0.0
   Win32 Version: 4.0.30319.1015 (RTMGDR.030319-1000)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1015 built by: RTMGDR
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
System.Data
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.237 (RTMGDR.030319-2300)
    CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true"
/>
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Hi,
That is as expected, the new tools require Configuration Manager 2012 R2 to work. From the download page of Configuration Manager 2012 R2 toolkit.
"Note: Items with an * are new in the R2 Toolkit and require Microsoft System Center 2012 R2 Configuration Manager for full functionality.
Server Based Tools
* DP Job Manager - A tool that helps troubleshoot and manage ongoing content distribution jobs to Configuration Manager distribution points.
* Collection Evaluation Viewer - A tool that assists in troubleshooting collection evaluation related issues by viewing collection evaluation details.
* Content Library Explorer - A tool that assists in troubleshooting issues with and viewing the contents of the content library"
So you need to upgrade to R2 before you can use the new tools.
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

SCCM 2012 SP1 CU4 migrated DP shows package status "unknown"

I have a SCCM 2012 SP1 CU4 environment and have shared SCCM 2007 distribution points.
Today I migrated one of the DP's which seems to work well.
However all my packages shows now the status "unknown" for this migrated DP.
This is a problem which should be fixed in CU4 according to the CU4 description. But it is not :-(
Any idea how to solve this ? R2 install ?

Some additional information:
I noticed that the package sources are still available at the "old" ditribution point share abd not on the new sccm 2012 distribution point share. When performing actions described in step 3 below the package becomes available on the distribution point
share......then i guess i can remove the content from the "old" distribution point share ????
I noticed that when a package got the status "unknown" for de migrated DP the following action fix the problem:
--> i remove the DP from the package and immediately add it again, the package status becomes "Successful".....hummm....ok....maybe a script could be created for this
I noticed that when a package got the status "unknown" and the package is also located on the "distribution point share" then following will fix the issue:
--> edit the package and remove the migrated DP and remove the checkbox for string on the distribution point share. Then add the DP again, click Apply and then set the checkbox for storing on the distribution point share and Apply again. Then wait and package
will become available Successful and the package will become available on the distribution point share
But i have 800 packages and 50 to be migrated DP's.....this is not a solution....but what is ????
Any help, ideas, tips, hints, recommendations ?
My overal thoughts are that migrating of a SCCM 2007 DP is not really working at all !!!!!
Or does someone has other experience with e.g. R2 installed ? If so then I will upgrade first...

SCCM 2012 SP1 errors when downloading updates

Currently using SCCM 2012 SP1 with CU2 and I am having some update download issue with Automatic Deployment Rules.
The Environment is:
Server 2008 R2
SCCM 2012 SP1 CU2 (Upgraded from SCCM 2012 CU2)
I created an Automatic Deployment Rule for Adobe Flash. Since I was having the same issue with Adobe Reader, when I published via SCUP to WSUS I chose not to sign the updates.
After publishing to WSUS I then sync SCCM, I see the updates and then in the ADR I had it download the updates and I see this error:
Authentication of file C:\Windows\TEMP\CABDEC5.tmp failed, error 0x800b0004 Software Updates Patch Downloader 8/15/2013 6:49:43 PM 3712 (0x0E80)
ERROR: DownloadContentFiles() failed with hr=0x80073633 Software Updates Patch Downloader 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Failed to download the update from internet. Error = 13875 SMS_RULE_ENGINE 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Failed to download ContentID 16845337 for UpdateID 16841530. Error code = 13875 SMS_RULE_ENGINE 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Now the funny thing is if I go to the update itself within update group that Flash is a member I can right click it and choose download and the error doesn't occur.
I observed that the UNC path for ADR Adobe flash, when the rule is ran, is populated with folders that have a name something like 44738297895427890.1 or 423154325378u867234789.1. I have come to realize that those are failed downloads. So for the
heck of it I then right clicked the update itself and chose download and it downloaded without issue. Now I'm guessing that when I chose to download directly from the update maybe the system is getting the update from adobe and not from wherever the rule was
trying to get it from. I then see the .1 removed from the directory name and there are updates within them.
Just for clarity here are the steps I go through from SCUP to Syncing...
Log in to WSUS server
Run SCUP as administrator
Get notified there are updates from Adobe and let SCUP download updates
Find the updates the specify the following publishing options
Full Content
Sign all software updates with a new publishing certificate .... (Is this necessary by the way?)
Then click Next
After that's done I then go to SCCM Manager Console and go to Software Updates and right click to Synchronize them.
After that's done then I run the ADR for Adobe Flash and when it goes to download the updates that's when the error occurs.
What am I missing?
Also, while I wait for help I just recently added the WSUS SCUP certificate to the SCCM server to see if by chance that fixes stuff. If it does then I'll post the results of adding the certificate to the SCCM server.
One other thing, is there a way to delete updates? When I was having this issue in the past, I went in to SCUP I marked the updates as expired and then deleted the updates. Went to SCCM and synchronized the updates and they went from not expired to expired
then I waited, maybe 30 days or so before I could add the updates back in.
Thanks for the help!

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
Have you seen the note at the bottom of this page about this error?
http://technet.microsoft.com/en-us/library/bb932193.aspx
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Office 2013 Professional Plus - 32 bit Deployment takes an unacceptable time to deploy in SCCM 2012 - SP1 CU3

We recently migrated over to SCCM 2012 SP1 - CU3 the first of the year from SCCM 2007 SP2. We have used SCCM in the past to deploy Office 2010 and had deployed Office 2013 to our IT Dept. before moving over to SCCM 2012. The deployment went as
expected. Now that we are ready to start deploying Office 2013 to our corporate workstations, the deployment time is running 4.5 hours to 5.5 hours from the local site server DP. I am afraid to find out what time we are looking at for remote DP's.
The three factors that are different is that our SCCM site server is virtual, it is running 2012 for the OS, and obviously SCCM 2012-SP1 - CU3. We are using the same package source files. Previous to a successful deployment we were
seeing hash mismatch errors which MS support pointed us to the nic driver on the VM was using E1000E and to change it to a VMX something driver.
So I guess my question is anyone else out there deploying Office 2013 ProPlus - 32 bit from this type of environment? Our previous deployment time for office was a little over an hour (not five hours). Any suggestions where to look to improve
the deployment time?
I am expected to deploy this in one week and have been working on these issues for weeks.

I see now that you are using a combination of scripts and ConfigMgr package/program.
The AppEnforce.log file is for use with the new ConfigMgr Application model.
Is there any reason that you don't use the new model for deploying Office 2013? It's a single step process and perfect for it. If you use the Office Customisation Tool you can customise what you like. The process will then uninstall Office 2010 and install
Office 2013.
This is how you do it
http://www.gerryhampsoncm.blogspot.ie/2013/03/sccm-2012-sp1-step-by-step-guide-part_9368.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM 2012 SP1 - Evil Folders in Reporting Services - What Are They and How to Remove Them

Hello All,
There are a lot of sub-folders in the http://CentralSiteSCCM/ReportServer. They are like:
<dir> Config_Mgr_CEN
<dir> Config_Mgr_CEN.OLD.0
<dir> Config_Mgr_CEN.OLD.1
<dir> Config_Mgr_CEN.OLD.10
<dir> Config_Mgr_CEN.OLD.100
<dir> Config_Mgr_CEN.OLD.1000
Only <dir> Config_Mgr_CEN is properly populated with the correct set of the default folders.
Would you be so kind to advise on:
What are they?
How to remove them?
What to do in order for them not to appear any more?
Thank you very much in advance!

Hi Mike,
I ran into an issue when I did the SP1 upgrade where a majority of our reports were duplicated. I created a script to delete these duplicate reports and I've adjusted it to work for your situation. You can find the original thread here, if you're interested:
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/dc9aa3b4-cea9-4a07-87ca-2795a2dbc04e
You'll need to know your SCCM site code and the server name to run this script.
# SCCM2012SP1-RemoveDuplicateSSRSFolders.ps1
# This script will connect to SSRS on a specified server and delete all folders that end with .OLD.*
# Used for SSRS cleanup after SCCM 2012 SP1 installation
# Script must be run from an account that has access to modify the SSRS instance
# 3/22/2013 - Mike Laughlin
# Resources used in writing this script:
# Starting point: http://stackoverflow.com/questions/9178685/change-datasource-of-ssrs-report-with-powershell
# API Documentation: http://msdn.microsoft.com/en-us/library/ms165967%28v=sql.90%29.aspx
# Previous script: http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/dc9aa3b4-cea9-4a07-87ca-2795a2dbc04e
# Define variables
$SiteCode = ""
$serverName = ""
# Set the value of $noConfirm to $True only if you don't want to manually confirm folder deletion. Use with caution.
$noConfirm = $False
# Safeguard
If ( $SiteCode -eq "" -or $serverName -eq "" ) { Write-Host "Enter the required information for the SiteCode and serverName variables before running this script." -ForegroundColor Red -BackgroundColor Black ; Exit }
# Connect to SSRS
$ssrs = New-WebServiceProxy -uri http://$serverName/ReportServer/ReportService2005.asmx?WSDL -UseDefaultCredential
# Get a listing of all folders in SSRS
$reportFolders = $ssrs.ListChildren("/", $True)
# Find all folders containing .OLD.*
$foldersToDelete = $reportFolders | Where { $_.Name -like "ConfigMgr_" + $SiteCode + ".OLD.*"}
# Quit if no folders are found
If ( $foldersToDelete.Count -eq 0 ) { Write-Host "No folders with .OLD.* found. Quitting." ; Exit }
# Show a listing of the folders that will be deleted
Write-Host "The following folders will be deleted from SSRS on" $serverName":`n"
$foldersToDelete.Name
Write-Host "`nTotal number of folders to delete:" $foldersToDelete.Count "`n"
# Get confirmation before deleting if $noConfirm has not been changed
If ( $noConfirm -eq $False )
$userConfirmation = Read-Host "Delete these folders from" $serverName"? Enter Y or N"
If ( $userConfirmation.ToUpper() -ne "Y" ) { Write-Host "Quitting, folders have not been deleted." ; Exit }
# Delete the folders
$deletedFolderCount = 0
Write-Host "Beginning to delete folders now. Please wait."
ForEach ( $folder in $foldersToDelete ) { $ssrs.DeleteItem($folder.Path) ; $deletedFolderCount++ }
Write-Host "Folders have been deleted. Total number of deleted folders:" $deletedFolderCount
Standard disclaimer: While this script worked just fine for me in my environment, I make no guarantees that it will work anywhere else. I've attempted to make this script as user friendly and generic as possible, but it may require slight tweaking to work properly.

Lync 2013 x64 silent client deployment via SCCM 2012 SP1

Greetings everyone!
I ran into a problem with Lync 2013 x64 silent deployment.
I need to provide every workstation with Lync 2013 client, so i decided to use deployment via SCCM 2012 sp1.
I created 2 msp files with OCT, one based on x86 Office 2013 Proplus, and other based on x64 Office 2013 Proplus.
Added them as applications to sccm software library.
Deployment of Lync 2013 x86 application was a success with over than 80% compliance.
But all Lync 2013 x64 automatic installations finish with different errors.
I created special device collection for workstations with office 2010 x64 and 2013 x64, because i can't install other architecture products once it has x64 product installed.
My membership query-rules for this collection:
Office 2013 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90150000-0011-0000-1000-0000000FF1CE}"
Office 2010 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90140000-0011-0000-1000-0000000FF1CE}"
My application deployment type points to setup.exe in office 2013 x64 installation folder, where i created msp file in updates folder via OCT and edited config.xml file in proplus.ww folder.
So my installation program looks like this setup.exe /adminfile updates\1lync.msp /config proplus.ww\config.xml
The same configuration works with Lync 2013 x86 deployment, except other setup folders.
When i try running installation program setup.exe with /adminfile and /config parameters locally, it installs successfully without errors or warnings.
I'm trying to find out problem source, does anyone have ideas what I am doing wrong?
Also i'm trying to reduce office 2013 installation folder size, what subfolders are necessary for Office 2013 proplus installation (still installing only lync with common files and tools)? Because now 3.5 GB package is quite hard to distribute to sccm secondary
sites with deployment point.
Thanks in advance.

Hi,
Here are some tips and tricks for your reference.
Tips and Tricks: Deploying Lync 2013 client using SCCM 2012 | Lync 2013 Client Customization for SCCM 2012 Deployment Package
http://zahirshahblog.com/2014/01/08/tips-and-tricks-deploying-lync-2013-client-using-sccm-2012-lync-2013-client-customization-for-sccm-2012-deployment-package/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
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.

Adding New SCCM 2012 SP1 Distribution Point To Replace Existing Distribution Point

Similar Messages

Maybe you are looking for