jeaostro

well something happens, its doesnt show any information when i run the report Do I need to link to another report?

Can i just copy paste this into a new Custom made report? in the SQL statement filed? Trying to run it but nothing happens?

thank u

Also another question that is a litle of topic here If i create a package called All windows XP updates, then a Management task called All WIndows XP updates. Can i download new updates to the All Windows XP updates packages, and these will be added to the All Windows XP Updates Management task, so it gets pushed to the clients, without needing to create a new management task. Or do i need to create a new Management task for each time i will deploy new updates? Thanks

Hello It worked perfectly when i removed the .Net updates, are there also other updates that do not work during OS deployment? What about Office updates, can i push all the Office 2007 Updates to computers during OS deployment, or are there also updates here that do not support installation during OS deployment? Thanks for the answers

To clear it up a lite bit. I know packages are supposed to be distributed down the hierarchy. But isn't it possible to stop this some how? I do not want all the software packages, collections, OS packages, boot images, and SUP packages to be distributed to all the primary child sites. Isn't it possible to control this some how? Some packages created in the central site, we would like to be only available to clients connected to the central site, and not visible on all the other primary child sites. Other administrators on the different primary child sites. thanks.

Hello I have configured a central parent site and a primary child site in a lab environment. The problem is as follows(or maybe it is supposed to be like this): When I create a software package at the Central site, and only distribute it to the central site distribution point. The packages shows up on the primary site with a lock on it. I can only view the package, not edit it. It shows up in the "Software Distribution -> Packages" on the primary child site. I do not want the packages that are created in the central site to appear in the primary site. How do i solve this?? ( ( I log on with the same user on both servers, is this the issue? domain administrator. We have one domain, but the computers and users are in different OU`s. Company 1 , Company 2, etc. Thanks for all the help you can give me. best regards jeaostro

Why do we need to add the Cumulative Hotfix 1 pack? We are only suppose to apply these Hotfix packs if we are having issues?

Well I'm just ignoring the error and creating the new Windows PE files manually. Everything else seemed to have been updated.

Should the following work? : Installed SCCM with SP1, then Updatet it to R2, and finally Updating it to SP2. Didn't do any configuring, would like to start the SCCM configuration when the site is running the latest version (SP2). The SCCM SP2 update procedure crashes when updating the X86 Windows PE images????? SCCM is running on a Windows 2008 Sp2 X64 server, with X64 SQL 2005 SP3. Any good ideas? Do I need to add the X86 Source files to the WDS? Only added X64 from source on the Windows 2008 dvd. Or isn't it supported to go from Sccm SP1, to R2 and then to SP2 without doing any configuration on the SCCM application. Heeeelp

yes there were some .net but none expired. Its just stops on "installing updates", and after 60 minutes it failes and moves on with the OS deployment.

Hello Followed the guide and I am trying to deploy mandatory software updates during OS deployment. The last October and November critical+security updates. Getting this error: The task sequence execution engine failed executing the action (Install Windows XP Critical and Security Updates) in the group (Install Software) with the error code 2147943860 Action output: 9F416}"' compiled in 'root\ccm\policy\machine' namespace Policy verification done GetIPriviledgedInstallInterface successful Refreshing Updates Successfully initiated RefreshUpdates operation Waiting for RefreshUpdates complete notification from Updates Deployment Agent FALSE, HRESULT=800705b4 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\installswupdate.cpp,1351) WaitForRefreshUpdatesComplete(spInstall), HRESULT=800705b4 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\installswupdate.cpp,1410) RefreshUpdates(), HRESULT=800705b4 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\installswupdate.cpp,998) InstallUpdates(pInstallUpdate, tType, sJobID, ulCookie), HRESULT=800705b4 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\main.cpp,279) Setting TSEnv variable SMSTSInstallUpdateJobGUID= Process(pInstallUpdate, tType), HRESULT=800705b4 (e:\nts_sms_fre\sms\client\osdeployment\installswupdate\main.cpp,349) Timedout waiting for updates refresh complete notification. The operating system reported error -2147023436: This operation returned because the timeout period expired. Anybody? Created a Deployment package with the updates, and Deployment management using a Deployment template witch targets my OS deployment collection. Thanks for the tips.

Do we also need to update the Windows the Windows PE images in WDS? Since the PE files in SCCM did not update by themselves?

looks like the solution, successfully updated the distribution point after doing this: http://support.microsoft.com/kb/950782/en-us :)

When i try to create a new boot images under "Boot Images" i get: Error: Data Source Information Source location: \\server\sms_aes\OSD\boot\i386\boot.wim Boot Image: 1 - Microsoft Windows Vista PE (x86) Error: Package Information Name: WindowsPE X86 Boot for SCCM Version: 1 Comment: test Error: Errors You can not import this boot image. Only finalized boot images are supported. For more information press F1. Seems like the boot.wim is the version from before SP2 update, or/and it is corrupt. How do i create a new boot.wim file that is the right version? Tried to reinstall WAIK, didn't help.

the boot image in \\server\SMS_AES\OSD\boot\i386\boot.wim doesn't seem to have been update when i updated to SP2. The same old file from when we created the site. Might there be a problem with the WAIK? Is it possible to remove it and install it again from an installer somewhere in the SCCM SP2 cd? I can enable or disable command line support, and still get the errors: Error: The wizard detected the following problems when updating the boot image. Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image The ConfigMgr Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "Failed to insert OSD binaries into the WIM file"; ErrorCode = 2152205056; File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; Line = 4262; ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; Operation = "ExecMethod"; ParameterInfo = "SMS_BootImagePackage.PackageID=\"AES0000C\""; ProviderName = "WinMgmt"; StatusCode = 2147749889; }; With or without drivers. Tried to remove the drivers and update, same error, tried to remove the files from the distrubution point and add them again. Same error....

the complete log: Error: Boot image to update: Microsoft Windows Vista PE (amd64) Error: Actions to perform: Add ConfigMgr binaries Disable Windows PE command line support Add drivers Error: Failed to import the following drivers: Intel® ESB2 SATA AHCI Controller Intel® ESB2 SATA RAID Controller Intel® PRO/1000 PT Dual Port Network Connection Intel® PRO/1000 PT Dual Port Network Connection Intel® 82567LM-2 Gigabit Network Connection Intel® 82567LM-2 Gigabit Network Connection ThinkPad PM Device Conexant 20561 SmartAudio HD Conexant 20561 SmartAudio HD Conexant 20561 SmartAudio HD Synaptics USB Human Interface Device Synaptics USB TouchPad PS/2 TrackPoint Intel® iSCSI Setup Driver Intel® iSCSI Setup Driver Intel® Advanced Network Services Virtual Adapter Intel® Advanced Network Services Protocol Intel® Advanced Network Services Virtual Adapter Intel® Advanced Network Services Protocol Intel® Advanced Network Services Virtual Adapter Intel® Advanced Network Services Protocol Intel® Advanced Network Services Virtual Adapter Intel® Advanced Network Services Protocol Intel® Advanced Network Services Virtual Adapter Intel® Advanced Network Services Protocol Intel® Advanced Network Services Virtual Adapter Intel® Advanced Network Services Protocol 82562EH based Phoneline Desktop Adapter Intel® PRO/10+ PCI Adapter Intel® PRO/100 Network Connection Intel® PRO/100+ Server Adapter Intel® PRO/100+ Management Adapter Intel® PRO/100 Network Connection Intel® PRO/1000 Gigabit Server Adapter Intel® PRO/1000 PT Dual Port Network Connection Intel® PRO/1000 PT Dual Port Network Connection Intel® PRO/1000 MT Desktop Adapter Intel® 82567LM-3 Gigabit Network Connection Intel® 82567LM-3 Gigabit Network Connection Intel® 82575EB Gigabit Network Connection Intel® 82575EB Gigabit Network Connection Intel® 82567LM-2 Gigabit Network Connection Intel® 82567LM-2 Gigabit Network Connection Intel® PRO/1000 Gigabit Server Adapter Intel® PRO/1000 PT Dual Port Network Connection Intel® PRO/1000 PT Dual Port Network Connection Intel® PRO/1000 MT Network Connection Intel® 82575EB Gigabit Network Connection Intel® 82575EB Gigabit Network Connection Intel® PRO/1000 PT Dual Port Network Connection Intel® PRO/1000 PT Dual Port Network Connection Intel® PRO/1000 Gigabit Server Adapter Intel® PRO/1000 MT Desktop Adapter Intel® 82567LM-3 Gigabit Network Connection Intel® 82567LM-3 Gigabit Network Connection Intel® 82575EB Gigabit Network Connection Intel® 82575EB Gigabit Network Connection Intel® 82567LM Gigabit Network Connection Intel® 82567LM-2 Gigabit Network Connection Intel® ESB2 SATA AHCI Controller Intel® ESB2 SATA RAID Controller Error: The wizard detected the following problems when updating the boot image. Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image The ConfigMgr Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "Failed to insert OSD binaries into the WIM file"; ErrorCode = 2152205056; File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; Line = 4262; ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; Operation = "ExecMethod"; ParameterInfo = "SMS_BootImagePackage.PackageID=\"AES0000D\""; ProviderName = "WinMgmt"; StatusCode = 2147749889; anybody?

tried this and got: Error: The wizard detected the following problems when updating the boot image. Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image Failed to install required packages into to the boot image The ConfigMgr Provider reported an error.: ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "Failed to insert OSD binaries into the WIM file"; ErrorCode = 2152205056; File = "e:\\nts_sms_fre\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp"; Line = 4262; ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook"; Operation = "ExecMethod"; ParameterInfo = "SMS_BootImagePackage.PackageID=\"AES0000C\""; ProviderName = "WinMgmt"; StatusCode = 2147749889; The files inn \\server\SMS_AES\OSD\boot\i386\boot.wim are from when we installed the site. In add/remove i can see that the WAIK was updated. :(

on properties on the Windows PE boot image in the Images tab, it says 6.0.6001.18000 Why didnt they get updated? And how do i update them?? Thanks.

I dident get any warning about WAIK?? THe SP2 just installed, we went from R2 til SP2 RTM. But the Boot images didnt update? They say version "1.0" that was the name i gave them when they were created. Is there another way i can see if these are updated?

So we don't need to stop advertisements or anything? Just run the update? That is almost to easy, used to always needing to do something. Will the agents on the computers be update by themselves? Or do we need to push the agent again to all computers? We do not have wsus or auto pushing of agents enabled. So just righ click collection and install client? Thanks

Also are there any pre requirements to be done before updating a R2 site to SP2? Like stopping the IIS7 site? Or just download, install, next next, finish? Best regards. Jean André

Hello When we update a primary site from R2 to SP2, will the client agents on the computers be automatically updated? Or do we need to push the agent again to all computers? (After creating the sccm agent package again like in your guide). And do we need to do this push in a special way? Or just right click all compuers, and choose install client("then reinstall even if installed") Best regards. Jean André

Here is my solution for Lenovo Computers: 1.Install and configure Lenovo Update Retriever on a server. Lenovo has good guides for this where you download the software. 2.Download Thininstaller 3.Create a software package that contains the thininstaller files(my software packages is the POC0002D below, this package contains all the thininstaller files) You can download Thininstaller from the same place that you download Update Retriever. Then do the following in the OS deployment task: 1. Under "Install Software" in the OS Deployment task, create a command line task that has the following command line: cmd.exe /c xcopy.exe \\SCCMSERVER1\SMSPKGE$\POC0002D\*.* c:\lenovo\thininstaller\ /E /D -> With timeout 5 minutes or so. 2.Create a new command line task that has the following command line: cmd.exe /c thininstaller.exe /CM -search A -action INSTALL -noicon -includerebootpackages 1,2,3,4 -repository \\TVSU-Server\tvsu -> With timout 120 minutes if you like to. The computers is deployed with all the Lenovo drivers and software you specified in the update retriever software. If you get a new Lenovo Model, just add the model to Lenovo Update Retriever and download the drivers/software with this tool. No need to add lenovo drivers or Lenovo software to sccm. best regards. jeaostro

If possible: Computer Name Computer User Computer Model Computer Manufacture Total Disk Space Free Disk Space Total Memory Im not any god at sql query so thanks for all I can get from you guys