SCCM4EVA

Hi all, I need to migrate my SCCM 2007 R2 Central Server (running on Windows 2008 Standard x64) to a new Win2008 R2 Server. I have version 4.00.6221.1000. It is parent to two child Primary sites (on Windows 2008 Std x64). The existing server is having issues but is still up and running. I also want to install SP2 in readiness for Windows 7/2008R2 deployment The SQL database it is pointing to is staying the same. Has about 2000 clients and in a single 2003 domain The Central Server has collections, boundries, packages, OSD's and advertisments. It is also the FSP / MP / SUP and Reporting point. However all clients point to either of the Primary Child sites as MP's depending on their location ie UK or France - and the Central is the fallback. I have read a couple of other posts on this scenario and want to list my steps and get your expert assessment/opinions please. Instead of doing a complicated side-by-side migration, can I do the following backup and restore? 1.do a full backup under Site Mantenenace / Tasks of the Central Server 2.Rename Windows Server holding the Central Site Server (should I do anything in SCCM itself) - or even just shut it down 3.Build new (windows 2008 R2) windows server with old central server windows name (new IP address) - What about the SCCM Site name - obviouly must stay the same? 4.Install vanilla SCCM - follow your guide for example (I used your guide to build the original servers :-)) 5.Perform restore from splash.hta or DVD 6.This won't import packages and I will have to redo the Roles this sound OK? then I install SP2 on the new central and then the child primary's. Many Thanks for helping

Hi all, I need to migrate my SCCM 2007 R2 Central Server (running on Windows 2008 Standard x64) to a new Win2008 R2 Server. I have version 4.00.6221.1000. It is parent to two child Primary sites (on Windows 2008 Std x64). The existing server is having issues but is still up and running. I also want to install SP2 in readiness for Windows 7/2008R2 deployment The SQL database it is pointing to is staying the same. Has about 2000 clients and in a single 2003 domain The Central Server has collections, boundries, packages, OSD's and advertisments. It is also the FSP / MP / SUP and Reporting point. However all clients point to either of the Primary Child sites as MP's depending on their location ie UK or France - and the Central is the fallback. I have read a couple of other posts on this scenario and want to list my steps and get your expert assessment/opinions please. Instead of doing a complicated side-by-side migration, can I do the following backup and restore? 1.do a full backup under Site Mantenenace / Tasks of the Central Server 2.Rename Windows Server holding the Central Site Server (should I do anything in SCCM itself) - or even just shut it down 3.Build new (windows 2008 R2) windows server with old central server windows name (new IP address) - What about the SCCM Site name - obviouly must stay the same? 4.Install vanilla SCCM - follow your guide for example (I used your guide to build the original servers :-)) 5.Perform restore from splash.hta or DVD 6.This won't import packages and I will have to redo the Roles this sound OK? then I install SP2 on the new central and then the child primary's. Many Thanks for helping

Hi, I have an issue with boot files not distributing to DP's. This is my error log from SMSTS.log (see below). However this is my question. Should the modified date of a boot.wim file change when you inject new drivers/change to enable support testing etc? (in the smspkgd$ and smspxeimages$ folder) - I can inject drivers into a boot.wim but can only distribute via the schedule and not via manually updating distribution point (get error about not finalized boot file) - IT appears to disctribute (messsages sa so) but nothing on the DP point. Filtering Content Locations. TSPxe 21/04/2010 16:59:43 1428 (0x0594) Found 0 DPs in subnet, 0 DPs in local site, 0 DPs in remote location and 0 Multicast DPs TSPxe 21/04/2010 16:59:43 1428 (0x0594) !lsDPList.empty(), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2134) TSPxe 21/04/2010 16:59:43 1428 (0x0594) FALSE, HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,1635) TSPxe 21/04/2010 16:59:43 1428 (0x0594) Content location request for PRI00007:16 failed. (Code 0x80040102) TSPxe 21/04/2010 16:59:43 1428 (0x0594) pTSPolicyManager->GetContentLocations( m_sPackageID, m_lSourceVersion, m_dwContentSourceFlags, slistContentLocations, slistHttpContentLocations, slistMulticastContentLocations, m_dwContentPackageFlags ), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2330) TSPxe 21/04/2010 16:59:43 1428 (0x0594) (*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2862) TSPxe 21/04/2010 16:59:43 1428 (0x0594) m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040102 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1207) TSPxe 21/04/2010 16:59:43 1428 (0x0594) Failed to resolve selected task sequence dependencies. Code(0x80040102) TSPxe 21/04/2010 16:59:43 1428 (0x0594) ResolveAndExecuteSelectedTaskSequence( 0, 0, 0 ), HRESULT=80040102 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2099) TSPxe 21/04/2010 16:59:43 1428 (0x0594) RunWizardForPXE(), HRESULT=80040102 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2383) TSPxe 21/04/2010 16:59:43 1428 (0x0594) oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80040102 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,936) TSPxe 21/04/2010 16:59:43 1428 (0x0594) Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80040102 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1105) TSPxe 21/04/2010 16:59:43 1428 (0x0594) Exiting with return code 0x80040102 TSPxe 21/04/2010 16:59:43 1428 (0x0594)

Ok, so I have re-added as a protected DP, how can I tell that my clients are using this DP to download my package?

ok thanks, I've deleted the role from my local server and will re-add as a protected DP and specify a couple of subnets.

hi Team, I am deploying a MS Hotfix via package deployment. I have created the package and configured the program within it. I have also deployed to several distribution points (servers). How do I ensure the package is pulled from the closest distribution point (server) and downloaded to CCM\cache folder of the PC's I am deploying to. It seems my package which is only a few hundred kb seems to take ages to download and run on the PC. CHeers

I have now manually recreated the SMSPXEIMAGES$ folder and SMSPKG folder under that. I have pushed some boot files down from my Central site server. I am still getting the error: "PXE Control Manager detected PXE service Point is not responding to PXE requests. The error is 16389". Would it be best to remove any packages and re-install the PXE service point component from the SCCM server?

Won't deleting my remoteinstall folder delete all my packages/images etc? I have successfully reinstalled it now with a new d:\remoteinstall directory. the SMSPXEimages should recreate then?

this is an iscsi drive too. Could be a timing issue.

it seems all my shares on the D:\ keep dissappearing. This is odd.

I did, and this is the point I am at where I can't configure the server as a WDS Server.

What do you think anyweb?

It they appeared after a reboot, Sinbce the WDSServer was trying to start.

IT did, I have deployed packages before. I am sure of it. However it would seem but then has been failing with increased regularilty. Looking through the Windows Deployment Services logs it would seem that it was been trying to startup and then it shuts down on a regular basis Erors include: ID 783 BINLSVC An error occurred while initializing the Auto Add database. ID 261 WDSPXE An error occurred while trying to initialize provider BINLSVC loaded from C:\Windows\system32\binlsvc.dll. If the provider is marked as critical the Windows Deployment Services server will be shutdown. --NOte- found MS article on this (http://support.microsoft.com/kb/927770) - although the servers haven't been moved in AD ID 265 WDPXE An error occurred while trying to initialize provider BINLSVC. Since the provider is marked as critical, the Windows Deployment Services server will be shutdown. Error Information: 0x906 ID 513 WDSServer An error occurred while trying to initialize provider WDSPXE from C:\Windows\system32\wdspxe.dll. Windows Deployment Services server will be shutdown. Error Information: 0x906 ID 257 WDSserver An error occurred while trying to start the Windows Deployment Services server. Error Information: 0x906 I am now thinkging I should re-initialised instead of uninstalling.

Firtsly, great site anyweb. Your instructions are fantastic, I have several SCCM servers in our environment at present. However my Primary SCCM Server, the WDS server service wouldn't start. Running this on Windows 2008 Standard I unsinstalled WDS and have reinstalled however I am unable to 'configure' the WDS server. IT simplay errors after trying to complete. I selected the same D:\RemoteInstall folder as before and choose respond to any client when configuring I hadn't removed the PXE Service Point either (I think I should've done this first) I am wondering what steps to take as have alot of images and packages configured that I have been deploying previously If you need more information I will give whatever is required Many thanks in advance