anyweb

Known Issue: Migrating from Windows XP to Windows 7 with USMT when used with ConfigMgr 2007 SP2 OS Deployment may not migrate all settings [in today's post Levi Stevens discusses an issue with USMT and Config Manager 2007 SP2] Problem Description When upgrading or reinstalling Windows XP to Windows 7 using USMT 4.0 to migrate system and user state, settings like Wallpaper and Network Printer mappings are not migrated. Running scanstate.exe from a folder other than the USMT - x86 - folder (the default for the Task Sequence) prevents scanstate.exe from finding the DLManifests folder to include system components like wallpaper and folder settings. These settings will not be migrated. USMT 4.0 must be run from a local folder containing the DLManifests folder. The User State Migration Tool (USMT) version 4.0 released with the Windows Automated Installation Kit (WAIK) version 2.0 and is a prerequisite for using OS Deployment with ConfigMgr 2007 SP2. Symptoms After migrating user state the wall paper or folder settings do not migrate. If you have enabled verbose logging (/v:5) you may see the following entry in ScanState.log: 2009-09-14 15:41:19, Info [0x000000] Downlevel Manifests folder is not present. System component settings will not be gathered. Workaround Copy the USMT binaries to local and use "Run Command Line" task sequence step to run scanstate.exe from the USMT\x86 directory (set the Starting In from "Run Command Line" to USMT\x86 folder). You will need two steps, one to copy the USTM folder to the local drive, and one to run USMT capture state. Example Task Sequence Save the below example as TSExample.xml, then import this into ConfigMgr. You will need to edit the task sequence to set the reference package that contains the RunScanState.bat example workaround script. <?xml version="1.0"?> <SmsTaskSequencePackage xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <BootImageID /> <Category /> <DependentProgram /> <Description /> <Duration>360</Duration> <Name>WorkAround</Name> <ProgramFlags>152084496</ProgramFlags> <SequenceData> <sequence version="3.00"> <referenceList> <reference package="SMS00001" /> </referenceList> <step type="SMS_TaskSequence_RunCommandLineAction" name="Run Command Line" description="" runIn="WinPEandFullOS" successCodeList="0 3010"> <action>smsswd.exe /run: cmd.exe /c md %systemdrive%\usmtsafe</action> <defaultVarList> <variable name="CommandLine" property="CommandLine" hidden="true">cmd.exe /c md %systemdrive%\usmtsafe</variable> <variable name="SMSTSDisableWow64Redirection" property="DisableWow64Redirection">true</variable> <variable name="_SMSTSRunCommandLineAsUser" property="RunAsUser">false</variable> <variable name="SuccessCodes" property="SuccessCodes" hidden="true">0 3010</variable> </defaultVarList> </step> <step type="SMS_TaskSequence_RunCommandLineAction" name="Run Command Line" description="" runIn="WinPEandFullOS" successCodeList="0 3010"> <action>smsswd.exe /run: cmd.exe /c md %systemdrive%\USMTbits</action> <defaultVarList> <variable name="CommandLine" property="CommandLine" hidden="true">cmd.exe /c md %systemdrive%\USMTbits</variable> <variable name="SMSTSDisableWow64Redirection" property="DisableWow64Redirection">false</variable> <variable name="_SMSTSRunCommandLineAsUser" property="RunAsUser">false</variable> <variable name="SuccessCodes" property="SuccessCodes" hidden="true">0 3010</variable> </defaultVarList> </step> <step type="SMS_TaskSequence_SetVariableAction" name="Set Task Sequence Variable" description="" runIn="WinPEandFullOS" successCodeList="0"> <action>tsenv.exe "OSDStateStorePath=%systemdrive%\usmtsafe"</action> <defaultVarList> <variable name="VariableName" property="VariableName" hidden="true">OSDStateStorePath</variable> <variable name="VariableValue" property="VariableValue" hidden="true">%systemdrive%\usmtsafe</variable> </defaultVarList> </step> <step type="SMS_TaskSequence_RunCommandLineAction" name="Run Command Line" description="" runIn="WinPEandFullOS" successCodeList="0 3010"> <action>smsswd.exe /run:SMS00001 xcopy * %systemdrive%\USMTbits /herciy</action> <defaultVarList> <variable name="CommandLine" property="CommandLine" hidden="true">xcopy * %systemdrive%\USMTbits /herciy</variable> <variable name="SMSTSDisableWow64Redirection" property="DisableWow64Redirection">true</variable> <variable name="PackageID" property="PackageID" hidden="true">7S000003</variable> <variable name="_SMSTSRunCommandLineAsUser" property="RunAsUser">false</variable> <variable name="SuccessCodes" property="SuccessCodes" hidden="true">0 3010</variable> </defaultVarList> </step> <step type="SMS_TaskSequence_RunCommandLineAction" name="Run Command Line" description="" runIn="WinPEandFullOS" successCodeList="0 3010"> <action>smsswd.exe /run: cmd /c runscanstate.bat %OSDStateStorePath% %systemdrive%</action> <defaultVarList> <variable name="CommandLine" property="CommandLine" hidden="true">cmd /c runscanstate.bat %OSDStateStorePath% %systemdrive%</variable> <variable name="SMSTSDisableWow64Redirection" property="DisableWow64Redirection">false</variable> <variable name="_SMSTSRunCommandLineAsUser" property="RunAsUser">false</variable> <variable name="SuccessCodes" property="SuccessCodes" hidden="true">0 3010</variable> <variable name="WorkingDirectory" property="WorkingDirectory">%systemdrive%\USMTbits\x86</variable> </defaultVarList> </step> </sequence> </SequenceData> <SourceDate>2009-10-21T19:33:43</SourceDate> <SupportedOperatingSystems /> <IconSize>0</IconSize> </SmsTaskSequencePackage> RunScanState.Bat @set USMT_WORKING_DIR=%~2%\USMTbits\x86 "%~2\USMTbits\x86\scanstate.exe" "%~1" /o /localonly /efs:copyraw /all /v:5 /l:%~2\windows\TEMP\SMSTSLog\scanstate.log /progress:%~2\windows\TEMP\SMSTSLog\scanstateprogress.log /i:%~2\USMTbits\x86\miguser.xml /i:%~2\USMTbits\x86\migapp.xml -- Levi Stevens http://blogs.technet.com/configmgrteam/archive/2009/12/01/known-issue-migrating-from-windows-xp-to-windows-7-with-usmt-when-used-with-configmgr-2007-sp2-os-deployment-may-not-migrate-all-settings.aspx

Computerworld - Microsoft's Windows ran to stay in place last month as Window 7's market share gains made up for the largest-ever declines in Windows XP and Vista, data released today by Web metrics firm Net Applications showed. By Net Applications' numbers, Windows 7's gains were primarily at the expense of Windows XP. For each copy of Vista replaced by Windows 7 during November, more than six copies of XP were swapped for the new OS. Meanwhile, Apple's Mac OS X lost share during November. But it was Microsoft's ability to retain its share in the face of record slumps in its older editions that was the news from Net Applications. Even though Windows XP lost 1.45 percentage points to end November with a 69% share, and Vista fell 0.2 percentage points to 18.6%, Windows kept its total operating system share at 92.5%, the same as in October. The declines in XP and Vista were both records in Net Applications' tallies, which because of a change in methodology instituted last July go back only two years. For Vista, November marked the second time in three months that the often-maligned operating system lost share. That trend, if accurate, means that the 2007 operating system has peaked, and will now, like XP before it, begin a slow, inexorable decline as it is replaced by Windows 7. more > http://www.computerworld.com/s/article/9141606/Windows_7_steals_biggest_chunk_of_share_from_XP

Late last week, a beta tester pointed out that Microsoft was planning to release its Office 2010 suite in June 2010, according to Fudzilla. Previously Redmond had only been quoted as saying "the first half of 2010" but more recently the company apparently posted the following message on one of the Office 2010 beta webpages: "The final version will be available to the public for purchase in June 2010." We browsed various Microsoft Office webpages, and even did a search, but we couldn't find the quote, so we contacted Microsoft directly. "We expect Office 2010 and related products to be generally available in June 2010," a Microsoft spokesperson confirmed with Ars. The software giant wouldn't get more specific than that, but that's how it always is with Microsoft: give a release year or a six month period, narrow it down to a month, and then unleash everything on a specific day, assuming no major delays. The most ambitious goal Microsoft is striving for with Office 2010 is making it available via a familiar experience across the PC, phone, and browser. Office 2010 is the first release of the productivity suite that will come in 32-bit and 64-bit flavors and on one DVD no less. In addition to the five editions of Office 2010 announced in July 2009, and the ad-supported one announced in October 2009, Microsoft is also working on the Office Web Apps, first demonstrated in October 2008: Web versions of Word, Excel, PowerPoint, and OneNote. full story > http://arstechnica.com/microsoft/news/2009/12/office-2010-confirmed-for-june-2010-release-1.ars

do you have network connectivity (ipconfig...) can you ping your servername ? you can troubleshoot pxe booting and connecting to the server to copy the logs here

i need a solution that can crawl through the thousands of images in several hundred folders and automagically apply a windows-noob.com © logo to each and it's got to be free can you help with that ?

are you sure thats the log file, doesnt look anything like a normal log file to me, please doublecheck and try again

great stuff thanks for sharing !

When using the "Capture Network Settings" task in a Configuration Manager 2007 (SCCM 2007) OSD Task Sequence on a PC that has teamed NICs, not all of the settings of the NIC may be captured properly. This mainly applies to DNS and WINS settings that are set statically. In these cases the settings are not captured and instead are set to obtain from DHCP when the network settings are restored via the "Apply Network Settings" task. http://blogs.technet.com/configurationmgr/archive/2009/11/30/the-capture-network-settings-task-in-a-configmgr-2007-osd-task-sequence-may-not-properly-capture-dns-wins-settings-on-teamed-nics.aspx

we can try this evening when i have time, contact me via msn.

no it can't you must enter the computername and MAC address or computername and GUID cheers niall

what custom settings are you trying to set exactly ?

Microsoft's latest round of security patches appears to be causing some PCs to seize up and display a black screen, rending the computer useless. The problem affects Microsoft products including Windows 7, Vista and XP operating systems, said Mel Morris , the CEO and CTO for the U.K. security company Prevx. Prevx was alerted to the problem by users of its security software last week, Morris said. Microsoft apparently made changes to the Access Control List (ACL), a list of permissions for a logged-on user. The ACL interacts with registry keys, creating visible desktop features such as a sidebar. However, the latest patches appear to make some changes to those registry keys. The effect is that some installed applications aren't aware of the changes and don't run properly, causing a black screen, Morris said. However, the latest patches appear to make some changes to those registry keys. The effect is that some installed applications aren't aware of the changes and don't run properly, causing a black screen, Morris said. Security applications seem to be particularly affected. Morris said users of other security products have also complained about the issue, even going so far as trying to reinstall the operating system to fix it. "If you've got this problem, it's massively debilitating," Morris said. Prevx has released software that fixes the registry to match the ACL settings, which should resolve the problem, Morris said. Users could do this on their own by modifying their registry settings, but making alterations to those settings is risky since it can severely affect how the operating system runs. full story > http://www.computerworld.com/s/article/9141568/Latest_Microsoft_patches_cause_black_screen_of_death

I havent tried it with R2 yet but Peter claims it works ok, did you triple check your webdav settings ?

if you want a computer to get an advertisement then that computer must be in a collection that the advertisement is advertised to if it isnt in that collection then you need to find out how that collection is gettings computers inside it, it can be in a variety of ways including direct membership or a query to place computers into the collection based on active directory security group membership in it's easiest form you could just create a direct membership for a computer to add it to a collection, or simply install right click tools and add the computer that way

do you mean that you want to change the site code on a client, or something else ?

what does this log tell us C:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log

how big are the files ?

here's a deep dive from Jannes aLink about what to expect in R3 http://www.jannesalink.com/blog1.php/2009/11/26/let-s-dive-deeper-in-configmgr-r3 cheers niall

looks like its seeing your windows deployment services server and not the pxe boot from sccm. check your psp role settings on the sccm server...

can you take a photo/screenshot of what you are seeing

so before it restarts stop it with F8 and copy the log to a network share

you'll have to configure the application to not look for updates prior to making a package out of it and distributing that package.

is webdav configured like so ? http://www.windows-noob.com/forums/index.php?/topic/490-how-can-i-configure-sccm-2007-sp1-in-windows-server-2008/

you have to create the MST file yourself using ORK.EXE (the office 2003 resource kit) some info about how to do that here > http://www.supinfo-projects.com/en/2005/mst_o2k3_uk/1/

Push the client to Targetted Collections In this example we will push an installation of the client to the All Systems collection, this is in a Lab so this is ok. In a production environment you will want to test this on small groups first and work your way up. Right click on the All Systems collection and choose Install Client set your options making sure that Always Install is selected click Finish when done to verify the installation of the new client is happening, on the clients open task manager and look for ccmsetup.exe after some time you can verify the client version on the client As the client starts getting installed, the report we used in the beginning will show the new numbers increasing