anyweb

How can I use USMT 3.0.1 in SCCM ? First download USMT from here http://www.microsoft.com/downloads/details...;DisplayLang=en * run the downloaded MSI by double clicking on InstallUSMT301_x86.msi, accept all defaults. Note: You need to install USMT on an XP client computer (you cannot install it on Windows Server) * create a share on your SCCM server called USMT * copy the entire USMT program files to your sccm server, eg: copy all files and folders within C:\Program Files\USMT301 from your XP computer to your SCCM server, create a package in SCCM called USMT 3.01 and point it to the folder you created on the server eg: \\server\source\usmt\x86 The USMT package does not need a program. you can then use that USMT package within Task Sequences to capture or restore the users state In the Operating System Deployment node, right click on Computer Association and create a new association between your Source and Destination pc's, once the association has been setup you can utilise your Task Sequence to do a State Capture or State Restore. You can view your active Computer Associations, by clicking on Computer Association, in the right pane, if you select an association, you can get Migrations details including when the State was captured, when the state was Restored and when the data will be deleted. Testing USMT When I test USMT with a SMP I separate the scanstate (capture) and loadstate (restore) sections of a task sequence into two separate task sequences targetted to two separate collections Steps in the Task Sequence You can create two separate task sequences to test Capture user state and Restore User State as below:- Capture State Task Sequence 1. Request State Store 2. Capture User State 3. Release State Store (without this you may get an error of 0x80004005) Restore StateTask Sequence 1. Restart the Computer step (use currently installed Operating System) 2. Request State Store 3. Restore User State 4. Release State Store that way i can quickly test usmt state capture and usmt state restore, you'll find that 9 times out of 10 your failures will be in the scanstate section and reading the scanstate.log and scanstateprogress.log files will assist you greatly. (Don't forget to Enable Verbose logging in the Task Sequence Capture User State step). Side-by-Side versus In-place SCCM Operating System Deployment supports the following scenarios: - New Machine (previously called New Computer) - Wipe-and-Load (previously called Refresh) - This is where users keep there existing hardware - Side-by-side (previously called Replace) - In-place migration Side-by-side You can initiate a Side-by-side migration by associating your source and destination computers and PXE booting the source, In-place To get an In-place migration, simply advertise your OSD Task Sequence to a computer while Windows is running, ie: do not PXE boot the computer, it will start the Task Sequence (or you start it in RAP) and automagically and your USMT status will be registered as In-place. Note that the details won't appear in the Computer Association pane immediatly, you can actually browse your SMP (state migration point) in Windows Explorer and see the data coming in, shortly after that, the association will be listed in the computer association node... Custom XML Examples Migrating the My Videos Folder The following is a custom .xml file named CustomFile.xml that migrates My Videos for all users, if the folder exists on the source computer. <?xml version="1.0" encoding="UTF-8"?> <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/CustomFile"> <component type="Documents" context="User"> <displayName>My Video</displayName> <role role="Data"> <detects> <detect> <condition>MigXmlHelper.DoesObjectExist("File","%CSIDL_MYVIDEO%")</condition> </detect> </detects> <rules> <include filter='MigXmlHelper.IgnoreIrrelevantLinks()'> <objectSet> <pattern type="File">%CSIDL_MYVIDEO%\* [*]</pattern> </objectSet> </include> </rules> </role> </component> </migration> Migrating Files and Registry Keys This table describes the behavior in the following example .xml file. <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/testfilemig"> <component type="Application" context="System"> <displayName>File Migration Test</displayName> <role role="Data"> <rules context="System"> <include> <objectSet> <pattern type="File">%ProgramFiles%\USMTTestFolder\* [uSMTTestFile.txt]</pattern><pattern type="File">%ProgramFiles%\USMTDIRTestFolder\* [*]</pattern> </objectSet> </include> </rules> </role> </component> <component type="System"> <displayName>Registry Migration Test</displayName> <role role="Settings"> <rules context="UserAndSystem"> <include> <objectSet> <pattern type="Registry">HKCU\Software\USMTTESTKEY\* [MyKey]</pattern> <pattern type="Registry">HKLM\Software\USMTTESTKEY\* [*]</pattern> </objectSet> </include> </rules> </role> </component> </migration> Migrating Specific Folders from Various Locations The behavior for this custom .xml file is described within the <displayName> tags in the code. <migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/test"> <component type="Documents" context="System"> <displayName>Component to migrate all Engineering Drafts subfolders without documents in this folder </displayName> <role role="Data"> <rules> <include> <objectSet> <pattern type="File"> C:\EngineeringDrafts\* [*]</pattern> </objectSet> </include> <exclude> <objectSet> <pattern type="File"> C:\EngineeringDrafts\ [*]</pattern> </objectSet> </exclude> </rules> </role> </component> <component type="Documents" context="System"> <displayName>Component to migrate all user documents except Sample.doc</displayName> <role role="Data"> <rules> <include> <objectSet> <pattern type="File"> C:\UserDocuments\* [*]</pattern> </objectSet> </include> <exclude> <objectSet> <pattern type="File"> C:\UserDocuments\ [sample.doc]</pattern> </objectSet> </exclude> </rules> </role> </component> <component type="Documents" context="System"> <displayName>Component to migrate all Requests folders on any drive on the computer </displayName> <role role="Data"> <rules> <include> <objectSet> <script>MigXmlHelper.GenerateDrivePatterns ("\Requests\* [*] ", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("*\Requests\* [*] ", "Fixed")</script> </objectSet> </include> </rules> </role> </component> <component type="Documents" context="System"> <displayName>Component to migrate all Presentations folder from any location on the C: drive </displayName> <role role="Data"> <rules> <include> <objectSet> <pattern type="File"> C:\*\Presentations\* [*]</pattern> <pattern type="File"> C:\Presentations\* [*]</pattern> </objectSet> </include> </rules> </role> </component> </migration> The above is via Technet Here is a list of the CSIDL (constant special item ID list) values and here is how USMT uses them. LoadState is slow ? If you are finding that the loadstate process is slow, make sure to enable verbose logging and verify if the miguser.xml file to include additional items for backuphas been modified, if it has verify that the conte4xt is set to User and not System eg: <!-- This component migrates Outlook PST Files --> <component type="Documents" context="System"> change to <!-- This component migrates Outlook PST Files --> <component type="Documents" context="User">

How does USMT store user state? Although there are a few different formats that one can choose from, we call all of them a "migration store." The different formats are as follows: Uncompressed migration store: choosing this format produces a containing a .dat file containing all files selected for the migration. Settings and other information are stored in an additional .mig file. Compressed migration store: choosing this format produces a directory containing a single compressed file containing all files and settings included in the migration. This file has a .mig extension and cannot be opened without USMT. Compressed and encrypted migration store: choosing this format results in the same experience as the compressed migration store, however the file is also encrypted with the provided key string. Below are the Scanstate command line options needed to select the above Migration Stores. Storage options StorePath Indicates a folder where to save the files and settings (for example, StorePath cannot be c:\). You must specify StorePath on the ScanState command line except when using the /genconfig option. You cannot specify more than one StorePath. /o Overwrites any existing data in the store. If not specified, ScanState will fail if the store already contains data. You cannot specify this option more than once on a command line. /encrypt /key:KeyString or /encrypt /key:"Key String" or /encrypt /keyfile:[Path\]FileName Encrypts the store with the specified key (password). Encryption is disabled by default. With this option, you will need to specify the encryption key with one of the following ways: /key:KeyString specifies the encryption key. If there is a space in KeyString, you will need to surround it in quotes. /keyfile:FilePathAndName specifies a .txt file that contains the encryption key We recommend that KeyString be at least 8 characters long, but it cannot exceed 256 characters. /key and /keyfile cannot be used on the same command line. /encrypt and /nocompress cannot be used on the same command line. Important You should use extreme caution with this option because anyone that has access to the ScanState command line script will also have access to the encryption key. For example: scanstate /i:miguser.xml /i:migapp.xml \\fileserver\migration\mystore /encrypt /key:mykey /nocompress Disables compression of data and saves the files to a hidden folder named "File" at StorePath\USMT3. Compression is enabled by default. You can use the uncompressed store to view what USMT stored, troubleshoot a problem or you can run an antivirus utility against the files. You should only use this option in testing environments because we recommend that you use a compressed store during your actual migration. /nocompress and /encrypt can not be used on the same command line. However, if you do choose to migrate an uncompressed store, LoadState will migrate each file directly from the store to the correct location on the destination computer — without a temporary location. For example: scanstate /i:miguser.xml /i:migapp.xml \\fileserver\migration\mystore /nocompress

Windows 7 Starter Edition, a sort of My First Operating System, always carried with it a massive braindead bug feature that limited the amount of applications you could simultaniously have open at just three. Yes, past tense, because someone over in Redmond apparently looked up and smelled the roses, and suggested removing this silly limitation. And so they did, according to Paul Thurrot. via > http://www.osnews.com/story/21547/Microsof...Three_App_Limit

those errors could be related to anything and you'll need to read the logs of each to see what it's complaining about, when installing an SCCM server and then configuring it you should expect some errors in the system status particularly if you are doing a few reboots.... cheers anyweb

use sysprep.inf to change the resolution, you could even define collection variables to do it for you in a more streamlined way for details of how that is done read Ronnis post here > http://myitforum.com/cs2/blogs/rpedersen/a...eployments.aspx please note that in his guide he has this bit sysprep.inf: [GuiUnattend] TimeZone=%LAB_OSDTimeZone% [ResionalSettings] SystemLocale=%LAB_OSDSystemLocale% SystemInput=%LAB_OSDSystemInput% [Display] XResolution=%LAB_OSDXResolution% YResolution=%LAB_OSDYResolution% which should read sysprep.inf: [GuiUnattend] TimeZone=%LAB_OSDTimeZone% [RegionalSettings] SystemLocale=%LAB_OSDSystemLocale% SystemInput=%LAB_OSDSystemInput% [Display] XResolution=%LAB_OSDXResolution% YResolution=%LAB_OSDYResolution% cheers anyweb

the easier way is KMS, but for that you'd need a special license with microsoft plus its a minimum of 25 vista desktops, you are using the OEM version of vista which uses an OEM key, and that is not designed for what you are doing, you should be using different Vista media (non oem, perhaps retail) with one license key... you see your problem is license based, what OEM are you using btw ? and what Vista Media are you using here ??? cheers anyweb

hi Jovin is AD on a separate server to your SCCM server ? if so you can ignore this bit and continue. cheers anyweb

step 1. disable the FIREWALL on the xp client for testing, you can modify the firewall properties later via a GPO. step 2. verify if the configmgr client is installed on the client by going into control panel, do you see any configmgr icons ? if the OS is 64bit the icons will be in the 32 bit control panel icons... step 3. if the client is present in step 2 above, then open the Configuration Manager icon otherwise skip to Installing the Configmgr Client step 6/ click on the actions tab, and select the machine policy retrieval and evaluation cycle and click initiate action. If you only have three or so actions listed don't worry, this means that the computer hasnt got received it's list of policies yet from the SCCM server Step 4. Click on the discovery data collection cycle and initiate the action. Step 5. wait a few minutes, if the status of your XP client in the All Systems collection (make sure to refresh the collection, press F5 after choosing Update Collection Membership) still says client=no then reinstall the client Step 6. If you need to reinstall the client, highlight the computer in the All Systems collection, right click and choose Install Client, place a checkmark in 'always install or repair' and next....

USMT saving the migration data locally instead of to your State Migration Point (SMP)? according to ZtiUserstate.log you can see the following: To resolve this and get your Migration data stored on the SMP, simply disable the Determine Local or Remote UserState step in your State Capture (Scanstate) Task Sequence, then remove the C:\MININT folder *see above* then re-run the USMT state capture task sequence

thats one problem with advertising software to USERS instead of COMPUTERS another problem is if the user uses multiples computers, that way you could have applications being installed all over the place and it would be very hard to manage, the recommended solution is to advertise your software to Computer objects within the Active Directory Security Groups but remember, when you advertise software you can make it mandatory or not, if its not mandatory the user gets the choice to install it or not (if you let them), if it's mandatory then it will get installed whether the user likes it or not cheers anyweb

This topic will be used to help document and troubleshoot State Capture errors only for instance, while doing a USMT scanstate today I got the following error: to fix, browse C:\ and verify that neither the _SMSTaskSequencer or MININT folder exist, if they do, delete them and run the State Capture task sequence again. The following two log files are very important for understanding what is happening while doing a ScanState: scanstate.log scanstateprogress.log You can locate those logs here C:\WINDOWS\system32\CCM\Logs Familiarising yourself with the contents of both files will allow you to troubleshoot Scanstate much better, plus if you are doing multiple test scanstates on the same computer, you should probably delete both files prior to running a new scanstate otherwise they will become large in size and thus take longer to process in Trace32.

odd, but i'm happy you have it working now , on with the show ! cheers anyweb

download it from here http://www.microsoft.com/downloads/details...;displaylang=en while you are at it get the Microsoft® Hyper-V™ Server 2008 R2 RC as well here http://www.microsoft.com/downloads/details...;displaylang=en

hi Murda it's not hard, here is how you do it http://www.myitforum.com/forums/SCCM_task_...m_199915/tm.htm cheers anyweb

first problem is this you need to set that in Client Agents...Computer Client Agent next, you have and theres many more errors, open the log yourself using Trace32 to see the errors in Red cheers anyweb

can you post your SMSTS.log file ? cheers anyweb

remove the PXE filter and add it again, if its windows server 2008 start the action by right clicking and choose to Run the MDT PXE filter with ADministrative priviledges

forget about the TS cal's, you need to get port forwarding to work first, did you manage to port forward TCP port 3389 from your ROUTER to your SERVER's local ip address ?

after you run the machine policy it will show up in a few minutes, hit F5 to refresh

to push the client do as follows use an account that has local admin priviledges on the client to install the client, for testing purposes in a lab a domain admin account will suffice, right click the computer in configmgr All Systems collection and choose 'Install Client' cheers anyweb

looks like this is how to do it, except you dont need a port RANGE you just need to forward the port i mentioned above http://portforward.com/english/routers/por...G2/Utorrent.htm cheers anyweb

most routers are different, so i'd need to know the model name of yours to tell you how... so what is it ?

no not the ip address of the router, do these steps 1. on the server open a web browser and goto http://www.whatismyip.com 2. on the ROUTER, you need to forward TCP port 3389 to the LOCAL ip address of the server 3. now you can attempt to RDP to the ip address obtained in #1 above from a computer outside of your lan (eg: on the wan...)

just RDP to the wan IP address of the server, have you tried that ?

got another one today, this happened after I rebooted the SCCM server (this is a test lab environment with dhcp and AD/DNS all running on the same box) my virtual and real clients were getting TFTP errors namely a quick troubleshooting session via Windows Server 2008's server manager showed no problems, all roles were functioning without problems a quick look at SCCM's system status did report that the PXE service point had problems restarted WDS server service, no change to the PXE boot problem restarted DHCP server service, no change restarted DNS server service, problem solved. f.y.i.