anyweb

that means unsupported, so you are doing something in windows that should be done in winpe or vice versa, i'll take a look at the log to confirm...i had a quick look at your log and didn't see any reference to the 0000032 failure, can you double check there's no more smsts*.log files ?

copy it to the usmt folder(s) give it a name like MyCustomXml.xml and redistribute your USMT package to your distribution points. Once done add the file to your Capture User Files and Settings step by selecting Customize how user profiles are captured. Click on Files and add the filename you specified.

add a custom XML file with exclusions like this one <!-- This component migrates Common Exclusions--> <component type="Documents" context="System"> <displayName _locID="miguser.userdata">Common Exclusions</displayName> <role role="Data"> <rules> <unconditionalExclude> <objectSet> <script>MigXmlHelper.GenerateDrivePatterns ("\Winnt\* [*]", "Fixed")</script> <script>MigXmlHelper.GenerateDrivePatterns ("\Windows\* [*]", "Fixed")</script> <pattern type="File">%CSIDL_WINDOWS%\* [*]</pattern> <pattern type="File">C:\MININT\*[*]</pattern> <pattern type="File">D:\* [*]</pattern> <pattern type="File">E:\* [*]</pattern> <pattern type="File">F:\* [*]</pattern> <pattern type="File">G:\* [*]</pattern> <pattern type="File">H:\* [*]</pattern> <pattern type="File">I:\* [*]</pattern> <pattern type="File">J:\* [*]</pattern> <pattern type="File">K:\* [*]</pattern> <pattern type="File">L:\* [*]</pattern> <pattern type="File">M:\* [*]</pattern> <pattern type="File">N:\* [*]</pattern> <pattern type="File">O:\* [*]</pattern> <pattern type="File">P:\* [*]</pattern> <pattern type="File">Q:\* [*]</pattern> <pattern type="File">R:\* [*]</pattern> <pattern type="File">S:\* [*]</pattern> <pattern type="File">T:\* [*]</pattern> <pattern type="File">U:\* [*]</pattern> <pattern type="File">V:\* [*]</pattern> <pattern type="File">W:\* [*]</pattern> <pattern type="File">X:\* [*]</pattern> <pattern type="File">Y:\* [*]</pattern> <pattern type="File">Z:\* [*]</pattern> </objectSet> </unconditionalExclude> </rules> </role> </component>

no way that i know of, correct.

you cannot migrate from SMS 2003 to ConfigMgr 2012 because there is no mechanism to do so within ConfigMgr 2012, and there won't be. There are capabilities built in to migrate from ConfigMgr 2007 however as described above.

is DNS working ?

search for smsts*.log

that's RC2 specific, just accept those three license agreements and continue

For all intents and purposes, this is only a minor change, and were this any other operating system or graphical environment, it would never warrant an entire news item. However, we're talking Windows, the most popular desktop operating system of all time, here. After 17 years of trusty service, Microsoft has removed the Start button from the taskbar in the upcoming Consumer Preview release of Windows 8. When Windows 95 was launched, one of its most important changes over Windows 3.11 and earlier versions was the inclusion of an entirely new graphical user interface. At the very heart of this interface and was the Start menu and the button that activated it. In the Windows 8 Consumer Preview, to be released at any moment now, the Start button is gone. The Consumer Preview has already been leaked all over the web, and it has been confirmed that it no longer contains the Start button (or orb, since Vista) or the Start menu. This is actually not all that surprising, considering the start menu's functionality had already been reduced severely in previous beta releases. Now, it's gone completely, with the Windows 7 taskbar in Windows 8's desktop mode now acting solely as a taskbar. The Verge has confirmed with its sources at Microsoft that the start button has been replaced by a hot corner (for mouse operation) and a gesture (for touch) which essentially serve as a means to switch between the Metro interface and the traditional desktop. On mouse activation, a thumbnail will appear of the mode you're switching to (Metro or desktop). The decision is supposedly not entirely final, and there's a minute chance that, given enough feedback, the button might return. Still, everything is pointing towards the full death of the Start menu and button. Let's face it - 17 years of service is an eternity in the computer world, and in all honesty, I do feel somewhat sad for its demise. For many, it's a cornerstone of computing, and now it's gone. We need to come up with a new "press start to shut down" joke. via > http://www.osnews.com/story/25581/Microsoft_Removes_Start_Menu_Button_from_Windows_8

well in both cases it's not an Error it's a warning, and you can always continue with warnings but not with Errors, good point though and good to see Microsoft is listening to bugs/dcr's filed and acting on them.

you can post your webservice related questions here, but no, it's fine to use it once specified correctly

depends on whether you are in windows pe or not, did you check if there was a SMSTSLOG subdir in ccm\logs ? at what point are you trying to get the log ? during the ts, or after it's failed

the exe is there, most likely in x:\sms\bin\x64\ try running it from there...

press f8, at the command prompt type this exactly x: cd %temp% cd smstslog cmtrace smsts.log

can you attach your smsts.log file it must list the problem (with your step)

press F8 at that point does it bring up a command prompt ? if so type ipconfig, do you get an IP ?

of course i do it all the time.

are you getting an ip ? what does the smsts.log file tell you ?

and it's much easier to do in Configuration Manager 2012 as you can see here

and if you click connect to site what happens ?

my current lab server (work supplied :-)) is a HP EliteBook 8560w Mobile Workstation, 16GB ram, 750gb internal hdd, 1.5tb external usb3 hdd with a soon to be added 256gb ssd via usb 3. It works ok but does lag occaisonally, the lag is all disc related, if i had the money i'd be going SSD the whole way

to add to the fun logon as a different user that the primary user, create a deployment type to uninstall the app based on a requirement that the user is not the primary user

please attach a complete smsts.log or smsts*.log file, it sounds like either a gpo or something else might be applying different regional settings on your computers (As they are in a different collection)

create one master and use separate WMI query based steps to install your device drivers (look at the task sequence XML file in this download for an example of that) no need at all to have several images, create your master image on virtual hardware, more info about that here to create you master image follow this guide:- Using SCCM 2007 Sp2 to deploy Windows 7 Deploy 7 (4 parts)

just click on the task sequence in the console, look at the references tab, you'll find your mdt toolkit files package there, locate the one that is the wrong version..