anyweb

is the service started ?

well when you try xcopy what happens ? what are you seeing happening, post logs if necessary

cmtrace is in the boot image by default now, just press F8 (make sure you enable this ability in the boot image properties) and you'll get a command prompt you can then cd to x:\sms\bin\x64\cmtrace.exe and launch it from there if a x64 boot image or x:\sms\bin\i386\cmtrace.exe for x86

thanks for the thanks always appreciated :-) you can show:- how to customise client settings and target collections with those custom settings show the new application model and how you can request apps with approval offline wim patching role based access control and lots lots more :-) cheers niall

is the site RPC using https or http ?

firewall blocking it perhaps ?

have you enabled Automatic site assignment in AD Forest discovery ?

are you sure that you are using the boot image that you enabled f8 on, in this task sequence ? when pxe booting the boot image you are using is listed while windows PE is loading, check the id, does it match ?

to speed things up you can force a manual Machine Policy update (use the coonfiguration manager client actions tab to do that)

look here then is the path full ? lack of space ? access denied ?

SQL server 2012 is not supported so i have no idea if it will work or not, likely it won't but good luck trying, as regards the WDS role it will be automatically installed by enabling PXE on the DP. Look at the distrmgr.log file to get details of that

i havnt tried what you are trying to do but you could configure configmgr as normal and enable PXE, then once done reconfigure WDS to point to your pxe chain, this may work, but i havn't tried it, so maybe you can try it ?

nope, it's not supported at this point, use the supported versions listed here.

if f8 doesnt work at which boot image are you using ? did you update the boot image to the dps after enabling command prompt support at what point during the task sequence are you pressing f8 ? have you tried another keyboard ?

interesting result and thanks for sharing.

don't worry about it, that's just the updates needed during installation, have you downloaded them separately already or ?

ok, well double check all my steps in the guide, you must have missed something or you are not telling me the whole story. as a troubleshooting step, you can open the wsus console and trigger a sync in ConfigMgr, what you should see is WSUS starting a sync, do you ?

triggering a sync causes Configmgr to ask WSUS to sync with Microsoft Update, do you need to configure proxy settings or something ?

the CAS should be the Active SUP.

you need to install the SUP role on both the CAS and the Primary, do that first, then perform a manual sync on the CAS. you must have missed something somewhere, can you double check all the steps i cover and also check your component status logs on both CAS and the Primary.

did you install the SUP role on both the CAS and your Primary ?

System Center 2012 was released was released yesterday and as a result all System Center 2012 products are available now! You can read more about the Microsoft Private Cloud here: http://www.microsoft.com/en-us/server-cloud/new.aspx and you can download the Microsoft Private cloud Evaluation software form the TechNet Evaluation Center: http://technet.microsoft.com/en-us/evalcenter/hh505660.aspx Microsoft also created a System Center 2012 track on Microsoft Virtual Academy. Currently there are 2 courses. But new courses will be added in the near future. Start learning System Center 2012 now: https://www.microsoftvirtualacademy.com/colleges/SystemCenter2012

if like me you are not able to attend MMS 2012 in Las Vegas, and you want to see what's going on, you can review the keynotes here. plus you can review many of the sessions as they are added right here. watching these you'll see the Windows Server 8 is renamed to Windows Server 2012 for example ! plenty to see, well worth watching cheers niall

if you followed the guide to the letter then just add computers to the collection, and they'll get the client, did you try it yet ?

read the below first (from http://technet.microsoft.com/en-us/library/dd560792%28v=ws.10%29.aspx) does it answer your questions above ? User Data This section describes the user data that USMT migrates by default, using the MigUser.xml file. It also defines how to migrate access control lists (ACLs). Folders from each user profile. When you specify the MigUser.xml file, USMT migrates everything in a user’s profiles including the following: My Documents, My Video, My Music, My Pictures, desktop files, Start menu, Quick Launch settings, and Favorites. Folders from the All Users and Public profiles. When you specify the MigUser.xml file, USMT also migrates the following from the All Users profile in Windows® XP, or the Public profile in Windows Vista® or Windows® 7: Shared Documents, Shared Video, Shared Music, Shared desktop files, Shared Pictures, Shared Start menu, and Shared Favorites. File types. When you specify the MigUser.xml file, the ScanState tool searches the fixed drives, collects and migrates files that have any of the following file name extensions: .accdb, .ch3, .csv, .dif, .doc*, .dot*, .dqy, .iqy, .mcw, .mdb*, .mpp, .one*, .oqy, .or6, .pot*, .ppa, .pps*, .ppt*, .pre, .pst, .pub, .qdf, .qel, .qph, .qsd, .rqy, .rtf, .scd, .sh3, .slk, .txt, .vl*, .vsd, .wk*, .wpd, .wps, .wq1, .wri, .xl*, .xla, .xlb, .xls*. Note The asterisk (*) represents zero or more characters. Access control lists. USMT 4.0 migrates access control lists (ACLs) for specified files and folders from computers that are running both Windows® XP and Windows Vista. For example, if you migrate a file that is named File1.txt that is read-only for User1 and read/write for User2, these settings will still apply on the destination computer after the migration. Important To migrate ACLs, you must specify the directory to migrate in the MigUser.xml file. Using file patterns like *.doc will not migrate a directory. The source ACL information is migrated only when you explicitly specify the directory. For example, <pattern type="File">c:\test docs</pattern>. Operating-System Components USMT migrates operating-system components to a destination computer that is running Windows 7 from computers that are running Windows XP, Windows Vista, or Windows 7. Note If you are using USMT 4.0 to migrate a user state to Windows Vista instead of to Windows 7, use the /targetvista option with the ScanState tool. Without the /targetvista command-line option, some operating-system settings can be lost during the migration. For more information, see ScanState Syntax. The following components are migrated by default using the manifest files: Accessibility settings Address book Command-prompt settings *Desktop wallpaper EFS files Favorites Folder options Fonts Group membership. For example, right-click My Computer, and then click Manage. USMT migrates the groups under Local Users and Groups for the users who are included in the migration. *Windows Internet Explorer® settings Microsoft® Open Database Connectivity (ODBC) settings Mouse and keyboard settings Network drive mapping *Network printer mapping *Offline files *Phone and modem options RAS connection and phone book (.pbk) files *Regional settings Remote Access *Taskbar settings Windows Mail. Microsoft Outlook® Express Mail (.dbx) files are migrated from Windows XP. *Windows Media® Player Windows Rights Management * These settings are not available for an offline migration. For more information, see Offline Migration. Important This list may not be complete. There may be additional components that are migrated. Note Some settings, such as fonts, are not applied by the LoadState tool until after the destination computer has been restarted. For this reason, restart the destination computer after you run the LoadState tool. Supported Applications Although it is not required for all applications, it is good practice to install all applications on the destination computer before you restore the user state. This makes sure that migrated settings are preserved. Note The versions of installed applications must match on the source and destination computers. USMT does not support migrating the settings of an earlier version of an application to a later version, except for Microsoft Office. Note USMT migrates only the settings that have been used or modified by the user. If there is an application setting on the source computer that was not touched by the user, the setting may not migrate. When you specify the MigApp.xml file, USMT 4.0 migrates the settings for the following applications: Product Version Adobe Acrobat Reader 9 AOL Instant Messenger 6.8 Apple iTunes 7, 8 Apple QuickTime Player 7 Apple Safari 3.1.2 Google Chrome beta Google Picasa 3 Google Talk beta IBM Lotus 1-2-3 9.8 IBM Lotus Notes 8 IBM Lotus Organizer 9.8 IBM Lotus WordPro 9.8 Intuit Quicken 2009 Money Plus Business 2008 Money Plus Home 2008 Mozilla Firefox 3 Microsoft Office Access® 2003, 2007, 2010* Microsoft Office Excel® 2003, 2007, 2010* Microsoft Office FrontPage® 2003, 2007, 2010* Microsoft Office OneNote® 2003, 2007, 2010* Microsoft Office Outlook® 2003, 2007, 2010* Microsoft Office PowerPoint® 2003, 2007, 2010* Microsoft Office Publisher 2003, 2007, 2010* Microsoft Office Word 2003, 2007, 2010* Opera Software Opera 9.5 Microsoft Outlook Express (only mailbox file) Microsoft Project 2003, 2007 Microsoft Office Visio® 2003, 2007 RealPlayer Basic 11 Sage Peachtree 2009 Skype 3.8 Windows Live® Mail 12, 14 Windows Live Messenger 8.5, 14 Windows Live MovieMaker 14 Windows Live Photo Gallery 12, 14 Windows Live Writer 12, 14 Windows Mail (only shipped with Windows Vista®) Microsoft Works 9 Yahoo Messenger 9 Zune™ 3 * A hotfix is available to support migrating Office 2010 settings. You should install this hotfix before you use USMT, when either the source or destination computer has Office 2010 installed. For more information, see Information about the User State Migration Tool (USMT) 4.0 update. What USMT Does Not Migrate The following is a list of the settings that USMT does not migrate. If you have a problem that is not listed here, see Common Issues. Application Settings <p class="subSection"> USMT 4.0 does not migrate the following application settings: Settings from earlier versions of an application. The versions of each application must match on the source and destination computers. This is because USMT does not support migrating the settings of an earlier version of an application to a later version, except for Microsoft Office, which USMT can migrate from an earlier version to a later version. Application settings and some operating-system settings when a local account is created. For example, if you run /lac to create a local account on the destination computer, USMT will migrate the user data, but only some of the operating-system settings, such as wallpaper and screensaver settings, and no application settings will migrate. Microsoft Project settings, when migrating from Office 2003 to Office 2007 system. ICQ Pro settings, if ICQ Pro is installed in a different location on the destination computer. To successfully migrate the settings of ICQ Pro, you must install ICQ Pro in the same location on the destination computer as it was on the source computer. Otherwise, after you run the LoadState tool, the application will not start. You may encounter problems when: You change the default installation location on 32-bit destination computers. You attempt to migrate from a 32-bit computer to a 64-bit computer. This is because the ICQ Pro default installation directory is different on the two types of computers. When you install ICQ Pro on a 32-bit computer, the default location is "C:\Program Files\...". The ICQ Pro default installation directory on an x64-based computer, however, is “C:\Program Files (x86)\...”. Operating-System Settings USMT 4.0 does not migrate the following operating-system settings. Local printers, hardware-related settings, drivers, passwords, application binary files, synchronization files, DLL files, or other executable files. Permissions for shared folders. After migration, you must manually re-share any folders that were shared on the source computer. Files and settings migrating between operating systems with different languages. The operating system of the source computer must match the language of the operating system on the destination computer. Customized icons for shortcuts may not migrate. Taskbar settings, when the source computer is running Windows XP. The following firewall settings when the source computer is running Windows XP. The Internet Connection Sharing setting is not migrated because it can make the network less secure if it is migrated to the destination computer. The firewall advanced-configuration settings are not migrated because of increased security risks. The Network Connections user interface will not completely refresh until you log off or press F5. Bridge settings are not migrated; for example, bridging a virtual private network to a second network adapter. You should also note the following: You should run USMT from an account that has administrative credentials. Otherwise, some data will not migrate. When running the ScanState and LoadState tools on Windows Vista and Windows 7, you must run the tools in Administrator mode from an account that has administrative credentials. If you do not run USMT in Administrator mode, only the user profile that is logged on will be included in the migration. In addition, you must run the ScanState tool on Windows XP from an account with administrative credentials. Otherwise, some operating-system settings will not migrate. To run in Administrator mode, click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. You can use the /localonly option to exclude the data from removable drives and network drives mapped on the source computer. For more information about what is excluded when you specify /localonly, see ScanState Syntax.