anyweb

hi Jason, to start off with, if you retain the same domain does everything migrate as expected for the user (leave out the /MD switch) ? cheers niall

first of all i'd recommend that you do not capture a domain joined image, this can cause issues with gpo's being applied to it amongst other registry specific changes, far better to capture a workgroup computer which can be domain joined in the deploy task sequence later, as regards the name, do you have a Set Computer Name step anywhere in the deploy task sequence and what does it contain

what delay did you set ? if you check any of the users states that are stored there, have they successfully migrated or not ? if there was a problem with the State Restore phase then the Release State Store step may not have run, if that step has not run then the timer (for state deletion) will not start which in turn will mean that the data will remain on the SMP

I met Garth Jones (ConfigMgr MVP) at the Global MVP Summit in Seattle and I heard about Ehansoft and one of the cool things they are doing is giving away reports every month, Garth is a very nice guy so return the favor and see what's on offer over there, want a cool report ? check it out - and vote - http://support.enhansoft.com/Forum/default.aspx?g=posts&t=29

in Software distribution, select the Package in question, locate the Program, right click on the program choose properties and on the General Screen you can see the Category option at the bottom of the window, simply select a category or type a new one to set it.

I would recommend still using the Build and Capture approach but change the way you are currently doing it, instead of build and capturing a FAT image, slim it down to only the bare essential FAT apps, such as Office 2010, Symantec Antivirus etc, do NOT include any drivers in this image and do not do any customisations to it, DO apply Windows updates to it and create this image on your favorite Virtual Platform (hyperV is good as it requires no drivers and you don't want any drivers in your master image), you will use this captured WIM image for the next stage, a Deploy Task Sequence. The Deploy task sequence will be used to deploy your thin captured image and should contain groups (which are based on WMI detection) of install drivers steps to install drivers for whatever models you intend to install on, this task sequence should also contain your Dynamic layers, where you install applications that change often like Adobe Acrobat or Adobe Reader (small apps generally). Any Windows customisations should take place in the Deploy Task Sequence, this way you can adapt/react to what your users need/want quickly without the need to recapture the image. well I hope that gives you some ideas cheers niall

you can have multiple pxe service points as long as they are not on the same subnet, are they ?

also check your client version matches the configmgr version, you mentioned sccm 2007 sp2 but in the screenshot it looks like the version of your client isSCCM 2007 sp1

no those screenshots were taken on a virtual machine as far as i remember, just press PrintScreen

Ever since the successful development and launch of Windows 7, Microsoft has become ever tighter-lipped about Windows development. Sure, it dropped the bomb about releasing Windows 8 for ARM, but that's it. Nothing on features or timetables (other than 'three years after Windows 7'). Well, the usually well-connected (inside Microsoft, that is) Mary-Jo Foley now claims to have a legit development roadmap - and it seems everything is on track for a Windows 8 beta in September 2011. The development timeline was passed on to Foley earlier this year by one of her sources, and it shows a tantalising development path for the next big Windows release. As rumours had already stated, milestone 2 was supposedly finalised yesterday or today, with development on the third milestone starting a week from today. This opens the door for a beta release in September of this year, right around Microsoft's Professional Developers Conference. "Milestone 2, according to the roadmap, took the Windows client team five months. If M3 takes another five months - which it might if it has to go through all the same coding/integration/fixing/lockdown steps as M2 did - that would put its completion date around the end of July," Foley theorises, "Factor in a month or so for any kind of private Community Technology Preview testing, and a beta around the time of this year's Professional Developers Conference - which I'm still hearing is slated for September 2011 - looks downright doable." That would put the final release of Windows 8 at around mid-2012, which isn't too bad. However, it also means that Microsoft's tablet offering will be a long time coming. While I personally think tablets are way overhyped, fact of the matter is that you need a tablet offering to be cool these days. Microsoft better have something to show for itself quickly, or else it'll find itself in the same position with tablets as they are in with smartphones now. via > http://www.osnews.com/story/24454/Windows_8_Beta_Could_Launch_September_2011

here's how to do it http://technet.microsoft.com/en-us/library/bb680919.aspx How to Enable or Disable Wake On LAN for a Site Applies To: System Center Configuration Manager 2007 Enabling Wake On LAN in Configuration Manager 2007 allows the primary site server to send wake-up packets for the following Configuration Manager activities: * Software update deployments * Software distribution advertisements * Task sequence advertisements Before you can enable these activities for Wake On LAN, you must enable the site for Wake On LAN. To prevent the site server sending wake-up packets, disable the site for Wake On LAN. To enable or disable the site the Wake On LAN, follow this procedure. To enable or disable Wake on LAN for a site: 1. In the Configuration Manager console, navigate to System CenterConfiguration Manager / Site Database / Site Management. 2. Right-click <site code> -<site name> and then click Properties. 3. On the Wake On LAN tab in the site properties dialog box, select the option Enable Wake On LAN for this site. 4. Click OK. noteNote For information about the options in the Wake On LAN tab, see Site Properties: Wake On LAN Tab.

excellent post Marcus thanks for sharing

When using the Use Toolkit Package task in a Configuration Manager 2007 task sequence, the Microsoft Deployment Toolkit 2010 Update 1 files package specified in the Use Toolkit Package task may not download correctly when the Distribution Point is on a Windows Server 2008 or newer server. The behavior will be different depending on the download method chosen under the Distribution Points tab in the properties of the advertisement: Download content locally when needed by running task sequence When the Task Sequence reaches the Use Toolkit Package task, the files for the package specified in the Use Toolkit Package will start to download and the progress bar will reach about 27%. The download will then all of a sudden stop, restart from the beginning, only to reach 27% again, and then restart again. On the third attempt it will the progress bar will get past 27% and finish downloading successfully. Reviewing the SMSTS.log on the client PC will show the following error: Downloaded file from http://<DP_Server>:80/SMS_DP_SMSPKG<Drive_Letter>%24/<Package_ID>/Tools/OSDResults/OSDResults.exe to D:\_SMSTaskSequence\Packages\<Package_ID>\Tools/OSDResults/OSDResults.exe InstallSoftware dwStatusCode>=200 && dwStatusCode<=299, HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\downloadcontent.cpp,1090) InstallSoftware WinHttpQueryHeaders() returns status code 404 (Not Found) InstallSoftware Download() failed with 0x80004005 InstallSoftware DownloadFile(sSourceFile, sDestinationFile, ulTotalSizeRequired, ulDownLoaded), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\downloadcontent.cpp,1175) InstallSoftware Error downloading file from http://<DP_Server>:80/SMS_DP_SMSPKG<Drive_Letter>%24/<Package_ID>/Tools/OSDResults/OSDResults.exe.config to D:\_SMSTaskSequence\Packages\<Package_ID>\Tools/OSDResults/OSDResults.exe.config InstallSoftware DownloadFiles(sSource, setDirs, setFiles, sDestination), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\resolvesource.cpp,2434) InstallSoftware Retrying download... InstallSoftware The above error will be displayed a second time, followed by the following line after the second failure: Tried all the available http based locations. SMB based locations will be attempted now. InstallSoftware After the second error and the above message, the download will be tried a third time and will then succeed. Examining the IIS logs on the distribution point server will reveal the following error: <GMT_Date> <GMT_Time> <DP_Server_IP> GET /SMS_DP_SMSPKG<Drive_Letter>$/<Package_ID_Of_Pacakage_In_Use_Toolkit_Package>/Tools/OSDResults/OSDResults.exe.config - 80 - <Client_IP> SMS+TS 404 7 64 15 Download all contents locally before starting task sequence When the advertisement is initiated either manually via the Run Advertised Programs control panel or automatically via a mandatory assignment, the download for the packages of the Task Sequence begins but never completes. Because the download for the Task Sequence packages never completes, the Task Sequence never begins or launches and the SMSTS.log is never created on the client PC. Reviewing client logs associated with downloading packages and executing the Task Sequence (execmgr.log, CAS.log, DataTransferService.log, ContentTransferManager.log) will not contain any errors. The client logs indicate that the downloads for the packages have begun, but the downloads never complete. Some of the client logs may have messages indicating that the downloads are in a pending or waiting state such as: DataTransferService.log Execute called for DTS job '{GUID}'. Current state: 'PendingDownload'. execmgr.log Execution Request for package <Task_Sequence_ID> program * state change from WaitingDependency to WaitingContent execmgr Persisting task sequence request for program * package <Task_Sequence_ID> in state WaitingContent execmgr If the advertisement for the Task Sequence was initiated manually via the Run Advertised Programs control panel, the Program Download Status window will show a progress bar that initially shows progress, but eventually stops and does not complete. The percentage complete will fail at a randomly different point each time the download is attempted. Examining the IIS logs on the distribution point server will reveal the following error: <GMT_Date> <GMT_Time> <DP_Server_IP> HEAD /SMS_DP_SMSPKG<Drive_Letter>$/<Package_ID_Of_Pacakage_In_Use_Toolkit_Package>/Tools/OSDResults/OSDResults.exe.config - 80 - <Client_IP> Microsoft+BITS/7.5 404 7 0 218 Running Bitsadmin.exe on the client PC with the following command line: bitsadmin.exe /list /allusers /verbose while the download is in the hung state will reveal the following error: ERROR FILE: http://<DP_Server>:80/SMS_DP_SMSPKG<Drive_Letter>$/<Pacakge_ID>/Tools/OSDResults/OSDResults.exe.config -> C:\Windows\system32\CCM\Cache\<Pacakage_ID>.<Source_Version>.<GUID>\Tools/OSDResults/OSDResults.exe.config ERROR CODE: 0x80190194 - HTTP status 404: The requested URL does not exist on the server.ERROR CONTEXT: 0x00000005 - The error occurred while the remote file was being processed. Access content directly from a distribution point when needed by the running task sequence No download issues are experienced when the advertisement for the Task Sequence is set to run from the distribution point (DP). Cause This issue is caused by the default configuration of IIS in Windows Server 2008 blocking the ability to download files that end in the extension .config. The Microsoft Deployment Toolkit 2010 Update 1 files package created by the Create Microsoft Deployment Task Sequence wizard and used in the Use Toolkit Package contains a file that ends in .config. The file is called OSDResults.exe.config and is located in the Tools\OSDResults directory of the package source files. When the option "Download content locally when needed by running task sequence" or "Download all contents locally before starting task sequence" is set on the advertisement for the Task Sequence, this will cause the file OSDResults.exe.config to be attempted to be downloaded via HTTP/HTTPS/BITS. However IIS will block this attempt since files ending in .config are blocked. When using the option "Download content locally when needed by running task sequence", it will attempt the download two times using HTTP/HTTPS/BITS before failing over to SMB. Since SMB does not use IIS, the third download attempt will then succeed. When using the option "Download all contents locally before starting task sequence", the BITS job gets hung on the error of not being able to download OSDResults.exe.config and does not fail over to SMB. This causes the whole download job to get in a hung state. Since the download for the packages of the Task Sequence never complete due to the hung state, the Task Sequence never launches. When the option "Access content directly from a distribution point when needed by the running task sequence" is used, HTTP/HTTPS/BITS is not used and all data transfers use SMB instead. Because SMB does not utilize IIS, the data transfers will succeed. Resolution To resolve the problem, follow the section "Configure the requestFiltering section on distribution points" in the following article: How to Configure Windows Server 2008 for Site Systems http://technet.microsoft.com/en-us/library/cc431377.aspx Specifically, on the Distribution Point server, configure IIS to allow files that contain the .config extension to be downloaded. This is done by changing the following line in the <requestFiltering> section of the applicationHost.config file from: <add fileExtension=".config" allowed="false" /> to <add fileExtension=".config" allowed="true" /> ===== The information above was published today in the following Microsoft Knowledge Base article written by Frank Rojas: via > http://blogs.technet.com/b/configurationmgr/archive/2011/02/23/configmgr-2007-quick-fix-a-package-specified-in-the-use-toolkit-package-mdt-task-does-not-download-correctly.aspx

i include it because my hta has scripts that depend on some of the other scripts within the scripts sub directory of the toolkit package, and because it's an easy way of doing it

does %SYSTEMDRIVE%\ = x: ? or c:\ have you checked ? by attaching the hta to the toolkit package i know that my hta plus the scripts it has will always be available when i have the mdt scripts available (which is what the use toolkit package step does), it downloads the content (the files/scripts) and sets some variables (path etc) I will do a webcast on this soon to clarify the steps involved

good stuff i look forward to our next session

have you copied the hta file itself into that path ? via the extrafiles method ? otherwise how can mshta.exe find the file ? sounds to me like mshta.exe is indeed running, but displaying nothing as it doesnt know where the hta file is you see, i refer to my hta file by adding it in the Use Toolkit package step

good points all round Marcus, i'll make sure my post links to this

and what's in your Start HTA step ? i see you are not using the mdt toolkit so how are you specifying the path to the actual hta file ?

where in the ts is it ? can we see a screenshot of the step in the ts

i guess the 64 bit version requires more ram, amazing but true interesting info Marcus how the testing going ? (contact me via mail about that)

are you trying to launch the HTA in winPE or in Windows ?

yup, and the moral of the story is if you are using language packs, add lots of ram, i found 1gb works but that was with virtual machines was this a vm or real hardware Marcus ?