anyweb

Until now, Microsoft has remained pretty tight-lipped on Windows 7 SP1, and the only information we have thus far on it is the leaked info from an array of sources, primarily Russian enthusiast site WZOR. However, today, amongst a flurry of virtualization-related chatter, Microsoft said a little something about SP1 for Windows 7 and Windows Server 2008 R2. On the Windows 7 front, nothing much was said asides from the fact that Windows 7 will simply include a wide array of “minor updates”. However, there’s some new features slated for Server 2008 R2. While not too much was said, Microsoft did announce that SP1 for Server 2008 R2 will bring 2 new virtualization-related technologies: RemoteFX and Dynamic Memory. RemoteFX is a set of RDP technologies that allows people working remotely to have the rich, immersive visual user experience as that of people working on a local desktop machine. Essentially, it is a set of graphics virtualization technologies that support Silverlight, 3D graphics, highly-synchronized audio, Windows Aero, and all media types without impacting performance, so you get the rich eye-candy of a local desktop machine without sacrificing performance. To find out more, check out the TechNet blog post. RemoteFX is the result of technologies Microsoft got their hands on upon acquiring Calista Technologies that they have built up on and improved. Microsoft has also announced a partnership with Citrix, which will allow Citrix to integrate Microsoft’s RemoteFX technology in its XenDesktop virtualization suite while also extending the capabilities of RemoteFX with HDX RichGraphics from Citrix, which optimizes the performance of graphics-intensive 2D/3D applications in virtualized environments. “By joining forces in desktop virtualization, Citrix and Microsoft can provide customers of all sizes with groundbreaking solutions that are profoundly simpler, richer and more cost-effective,” said Gordon Payne, senior vice president and general manager, Desktop Division, at Citrix Systems. “Today’s announcements mark a historic milestone in our 20-year relationship that will dramatically simplify desktop computing for years to come.” more > http://geeksmack.net/microsoft/1157-microsoft-announces-sp1-for-windows-7-and-windows-server-2008-r2 and > http://windowsteamblog.com/blogs/windows7/archive/2010/03/18/talking-about-service-pack-1-for-windows-7-and-windows-server-2008-r2.aspx

did you configure the software update component yet ?

i believe that message is hard coded

how are you doing 3. Reinstalling the client and then rebooting - again with no network cable in. ? any batch file involved ?

you could try and mount the wim, add the bits you want, and save it

you should really use the sp2 dvd, it supports windows 7 and windows server 2008 r2 and its the current release of SCCM cheers niall

you need the full System Center Configuration Manager 2007 SP2 DVD (or iso) the R2 release is only a 27mb or so update for the full install of SCCM 2007 listed above cheers niall

have you checked if any logon (startup) script or OU policy is doing this ?

why are you trying to add boot images from dvds ?

well you could tweak it to autogenerate a new computer name without user input based on several factors, you could use computer variables, collection variables or other ideas.. that's up to you to script cheers niall

hi Anna and welcome to the ever growing forum, to your questions: yes, keep them separated even in a lab, it's better practise and with virtualisation (vmware or hyperv) it's easy to create new servers. by default the i386 boot images are in \\sccm_server\sms_XXX\OSD\boot\i386 where XXX is the SCCM Site Code cheers niall

try adding a boot image from the two default boot images that are included with sccm first, does that process work ? that process is outlined here

depends on where you look, for site description yes, but the important bit is R2 Installed: Yes

maybe this will help ? http://www.windows-noob.com/forums/index.php?/topic/1133-setting-computername-during-deployment/

it's all about time and i don't have much time between work, family and here, but it's on plan so please be patient

If you are interested in testing the Internet Explorer 9 then checkout this link Speed Demos Take full advantage of your hardware with background compiled JavaScript * Flying Images * Text Size Animated * Test Justification Animated * Map Zooming * Pulsating Bubbles HTML5 Demos Deliver rich interoperability with the next generation of Web standards * Border Radius * CSS3 Selectors * DOM Events * DOM Style * HTML5 T-Shirt Designer Graphics Demos Create next-generation experiences with GPU-powered HTML5 graphics * Falling Balls * SVG–oids * Business Charts * Organization Chart * Atlas zur Europawahl

does this help to clarify it ?

works fine here as before can one of you post your netsetup.log file here ? is the domain join user correctly specified ? are you specifying the OU to join ?

25 is the minimum number, once you've reached that the KMS server will happily activate them all

the first package, which I mentioned above

via http://support.microsoft.com/kb/839513 Follow these steps to adjust the size of the cache, to modify the location of the cache, or to remove all cache content: 1. On the SMS 2003 Advanced Client computer, click Start, click Settings, and then click Control Panel. 2. Double-click System Management. 3. In System Management Properties, click the Advanced tab. 4. Follow one or more of the following steps: * To adjust the size of the cache, under Temporary Program Download Folder, click the slider bar to change the Amount of disk space to use setting. * To modify the location of the cache, click Change Location, and then specify a new folder. * To remove all cache content, click Delete Files. To modify the Advanced Client cache settings for the whole SMS 2003 site, we recommend that you use a script. You can deploy a script by using an advertisement, by using Group Policy, or as part of the logon process. For more information about programmatically modifying these cache settings and for sample scripts, search the SMS 2003 Software Development Kit (SDK) for "CacheInfo." To obtain the SMS 2003 SDK, visit the following Microsoft Web site: http://www.microsoft.com/downloads/details.aspx?FamilyID=58833cd1-6dbb-45bb-bb77-163446068ef6&

no its not required, unless you intend to deploy Windows Updates via SCCM's sup role (software update point) in which case it is required.

try setting the wds service to start with delayed start

what do you need to run once ? have you looked at any of the built in commands via unattend.xml check this post on msfn.org http://www.msfn.org/board/topic/139150-working-unattendxml-and-applications-installs/ and I quote: also checkout this from Technet > about SetupComplete.cmd > http://technet.microsoft.com/en-us/library/cc766314%28WS.10%29.aspx Add a Custom Script to Windows Setup You can add custom scripts to Windows Setup that can be configured to run in different circumstances. You can run a custom script: * Immediately after Windows Setup completes. * If Windows Setup encounters a fatal error. Run a Custom Script after Windows Setup Completes You can make further customizations after Windows Setup completes by adding commands to the %WINDIR%\Setup\Scripts\SetupComplete.cmd file. This file enables you to install additional applications, run custom Windows scripts (cscript/wscript), or make other modifications to the system before a user logs on. Note Commands in the Setupcomplete.cmd file are executed with local system privilege. After Windows is installed, but before the logon screen appears, Windows Setup searches for the SetupComplete.cmd file in the %WINDIR%\Setup\Scripts\ directory. If a SetupComplete.cmd file is found, the file is executed. Otherwise, installation continues normally. Windows Setup logs the action in the Setupact.log file. Note You cannot reboot the system and resume running SetupComplete.cmd. Setup does not verify any exit codes or error levels in the script after executing SetupComplete.cmd. The functionality of Setupcomplete.cmd differs from the RunSynchronous and RunAsynchronous commands in that Setupcomplete.cmd runs after Windows Setup completes while the RunSynchronous and RunAsynchronous commands run during Windows Setup. Run a Custom Script if Windows Setup Encounters a Fatal Error If Windows Setup encounters a fatal error, you can configure Setup to automatically launch a script that contains custom commands or actions. A fatal error is an error in which Windows Setup is prevented from completing the installation. This functionality is useful when you automate the installation of many systems at the same time. By enabling this functionality, you can immediately detect when an error occurs during Windows Setup and run custom actions. If Setup encounters a fatal error and is prevented from completing the installation, Setup searches for a command script in the following directory: %WINDIR%\Setup\Scripts\ErrorHandler.cmd. One of two actions will occur, depending on whether the script is found. * If the script is not found, a dialog box is displayed with the error text. A user must dismiss the dialog box before Setup exits. * If the script is found, the script executes synchronously. No dialog box or error text is displayed. After the ErrorHandler.cmd script completes, Windows Setup exits. Depending on the phase of Windows Setup, the computer will return to the environment from which Setup was executed (for example, a downlevel operating system or Windows PE). There are several ways that you can add the ErrorHandler.cmd file by using the $OEM$ directory structure. * Create a Sources\$OEM$\$$\Setup\Scripts folder in the Windows distribution. Copy the ErrorHandler.cmd file to this directory. For more information about using $OEM$ files, see Add Content to $OEM$ Folders. * Create a temporary folder that contains a $$\Setup\Scripts folder structure. Copy the ErrorHandler.cmd file to this directory, and then run Windows Setup with the /m:temp_folder parameter. For example, if you create C:\Temp\SetupFiles\$$\Setup\Scripts\ErrorHandler.cmd, use the following command: setup.exe /m:C:\temp\SetupFiles For more information about the setup.exe /m parameter, see Windows Setup Command-Line Options. There may be instances when Windows Setup encounters more than one error and runs the ErrorHandler.cmd script more than once. When developing the code for ErrorHandler.cmd, ensure that you can run this script multiple times. Sample SetupComplete.cmd file here's a sample Setupcomplete.cmd file from srvops SetupComplete.cmd @echo off cd\ start /wait regedit.exe /s c:\windows\setup\win7regsettings.reg exit win7regsettings.reg Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] "ConsentPromptBehaviorAdmin"=dword:00000000 [HKEY_CLASSES_ROOT\Folder\shell\Cmd Here] @="Command &Prompt" [HKEY_CLASSES_ROOT\Folder\shell\Cmd Here\command] @="cmd.exe /k pushd %L" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management] "DisablePagingExecutive"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SL] "SkipRearm"=dword:00000001 ;1st setting - Turn off UAC Prompt for Admin Elevation ;Next 2 settings - Create a Command Prompt entry on the right click menu ;4th setting - is to put the Windows Kernel in memory. Only do this if you have more than 512MB of RAM ;5th setting - setting this to 1 allows for 8 "rearmings of activation" in Vista Business and Ultimate editions. ;A setting of zero allows for only 3 rearms. cheers niall

Just in case any of you try this, if you have a task sequence with a 64 bit boot image assigned to it, and you try to deploy an X86 (32 bit) image, the task sequence will fail, as it's not supported. It will fail in the Apply Operating System step with an error simlar to the following: To resolve, simply change the boot image for the task sequence to X86 and try again.