anyweb

Please note that this guide is designed to get you Deploying Windows XP with SCCM in a LAB Environment as quickly as possible. This guide is provided as is, if you find any errors please report them in the forums. In a production environment please consult Technet for best practise, see below links: Operating System Deployment: Operating System Deployment in Configuration Manager Overview of Operating System Deployment Configuration: System Center Configuration Manager 2007 Best Practices: Configuring Configuration Manager Sites for Best Performance Checklist for Security Best Practices Best Practices for Central and Primary Site Hardware and Software Configuration Best Practices for Operating System Deployment This guide assumes you have installed SCCM 2007 SP1 and then configured it as outlined here in Part 1 you must then do the additional configuration outlined in Part 2, and you must have completed the final configuration tasks in Part 3. Lastly you must be able to deploy an application using SCCM 2007 and you should have reviewed part one and part two of Deploying Windows Vista, which covers setting up the PXE Service point. Note: In this guide I've used the en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso available on MSDN, this is the Retail version of XP, you should really use the VL (Volume License edition) in conjunction with your VL key to deploy XP. Note: This Deploy XP guide will create a build image of Windows XP using the XP cd mentioned above. Once the image is created we will Capture the image. This whole process is known as 'Build and Capture'. The captured image can then be used in a separate task sequence to Deploy XP. Import XP SP3 as an Operating System Install Package In the Operating System Deployment node of ConfigMgr, right click on Operating System Install Packages and choose Add Operating System Install Package. click on browse and browse to the network share where you have previously copied the XP SP3 CD contents to... (in my case that's \\WIN-AE2V1IRN067\iso\Xp sp3 retail) once you have the Data Source correctly specified, click next on the General Page fill in some details about this XP SP3 image... review the summary, click next and click close at the confirmation screen.

Please note that this guide is designed to get you up and running with SCCM in a LAB Environment as quickly as possible, so server roles are not going to be separated unless otherwise stated. This guide is provided as is, if you find any errors please report them in the forums. This guide refers to Service Pack 1 but you should use the latest version available currently which is Configuration Manager 2007 Service Pack 2. The latest version of this guide can always be found at http://www.windows-n...ws-server-2008/ In a production environment please consult Technet for best practise, see below links: Prerequisites: Prerequisites for Installing Configuration Manager Configuration: System Center Configuration Manager 2007 How to Configure Windows Server 2008 for Site Systems Best Practices: Configuring Configuration Manager Sites for Best Performance Checklist for Security Best Practices Best Practices for Central and Primary Site Hardware and Software Configuration Best Practices for Operating System Deployment Checklists: Example Configuration Manager Installation Checklist Example Configuration Manager Upgrade Checklist This guide assumes that you have first setup Windows Server 2008 and configured it for Active Directory, with DHCP (you only need steps 1 and 2 this guide). If you want to deploy operating systems within SCCM you will then also need the Windows Deployment Services installed, and that is covered in steps 3 and 4 of this guide). You must have installed and configured IIS (for SCCM) and installed SQL Server 2005 SP2 (or SQL Server 2008 with this hotfix) and WSUS (you can install WSUS later if you want, it's only required for the SUP role). Please note: WSUS SP2 is a role within Server 2008 R2 so if you are using Server 2008 R2 you can install WSUS Sp2 by adding the role. If you are thinking about hosting SQL Server on another server than the SCCM server then please read this post. You should also read the SCCM prerequisites on Technet. We will be using the MSDN version of SCCM 2007 Sp1 namely en_system_center_configuration_manager_2007_with_service_pack_1_x86_dvd_x14-66461.iso so burn it to DVD or mount it in Daemon tools (or similar). Part 1. Run the prerequisite checker and fix the warnings/errors. When the menu appears, click on Run the prerequisite checker, we'll do this to see if our Windows Server 2008 needs any additional tasks performed prior to installing SCCM 2007 sp1. enter your servername as below (leave OUT the instance name or you may get errors explained in the Final Note) this gave me two prerequisites which needed looking at, the AD Schema extensions, Microsoft Remote Differential compression. If you want to get more details of the problems identified, then check c:\ConfigMgrPrereq.log (and c:\ConfigMgrSetup.log) or double click each warning/error in turn to get a short description (scrollable) of the problem. My first problem was that I needed to extend the Active directory schema, to do so I followed this guide. Once I had extended the active directory schema, I ran the prerequisite checker again, That left me with the RDC error, That led me here and that in turn had this info To add Remote Differential Compression to site servers and branch distribution points In Server Manager, on the Features node, start the Add Features Wizard. On the Select Features page, select Remote Differential Compression, and then click Next. Complete the rest of the wizard by clicking install then close. Now run the prerequisite checker again and the RDC error should be gone Once you have no warnings or errors, please proceed to Part 2. Final Note: if you entered the instance name at the start of this guide, you may get an error which states The Technet page for Setup Prerequisite checks states:-

Before starting this, make sure to backup all your SQL databases, any problems arising from doing this are your own responsibility, always test this on a test lab computer scenario before doing it in your business environment. Download the following from Microsoft connect or your MSDN downloads area. en_sql_2005_std_x86_dvd.iso and en_sql_server_2005_sp2_x86_cd.iso burn them to DVD/CD or mount them using tools such as Daemon tools. Step 1. Run the upgrade advisor to see what issues may need to be resolved Start the SQL Server 2005 Standard edition DVD and select Install SQL upgrade Advisor from the list of options. When the wizard appears click next accept the license aggreement enter/verify your registration information click next when asked what features to install (go with the default) choose install to install the SQL Upgrade Advisor once done click on Finish Now that it's installed, let's run it, so click on Start, All Programs, Microsoft SQL Server 2005, SQL Server 2005 Upgrade Advisor When the Upgrade Advisor splashscreen opens, click on Launch Upgrade Advisor Analysis Wizard. This will launch another wizard click next to continue choose the components you want to analyze (i selected all) when asked how the Upgrade Advisor should connect go with the default settings unless you have changed them previously when installing SQL click next when prompted for what databases to analyze if you get an error about not finding the notification services hit the back button three times and remove the checkmark from 'notification services' and continue again. click next for the DTS parameters view the confirmation and click Run to start... once done you can click on Launch Reprt to see the details viewing the report will allow you to see what components to change before attempting the actual SQL upgrade.

Please note, this is for lab testing purposes, use it at your own risk, always backup your SMS database and site before attempting any radical changes such as an upgrade. If you break your production setup by doing anything here I am not responsible, use at your own risk. Test always in a LAB first. Before performing the steps below you should perform a test DB (database) upgrade as detailed below.WARNING: the following can corrupt the database if used on a production database. It cannot be used more than once on the same database copy. Step 1. Test the DataBase upgrade Note you should have backed up your SMS database using SMS database backup prior to running this. In addition, copy your SCCM 2007 SP2 media to a local folder for the DB upgrade process. On your SMS 2003 Server:- Open SQL Server Management Studio. Right click Databases select Restore Database. For Database (type in): CopyofServerName (replace ServerName with your SMS server name) Select From Device, use ellipses button to browse. Click the Add button. in Files of Type, use drop down to select all Files(*) Expand the location where your SMS database is backed up to, for example C:\SMS_BACKUP\SiteDBServer select the SMSbkSQLDBsite.dat file. Click Ok, and Ok again. Select Restore Box to check. Ok, and Ok to Restore was successful Open Command prompt and Browse to your SCCM Sources Media folder. SCCM 2007 with SP2\SMSSETUP\BIN\I386 setup.exe /testdbupgrade CopyofServerName Answer YES, Click Begin Upgrade Open log files: C:\ConfigMgrPrereq.log, C:\ConfigMgrSetup.log A window should appear and say successful If unsuccessful stop here, if successful, move forward. Clean up CopyofServerName Database. Right click CopyofServerName database, select Delete, leave defaults, click ok. Step 2. Start the Upgrade First of all download the iso from your MSDN account or Microsoft Connect. once done, burn it to DVD or mount the ISO using Daemon tools or similar. Before starting the process you'll need to know the prerequisites, and thankfully there is a prerequisite checker included on the DVD. Next you should run the prerequisite checker so let's run that and see what it says If like me you already have an SMS 2003 server setup then it will automatically choose the upgrade option, as this server is the only SMS site we will click ok to continue. After some scanning it will present you with a results page, double clicking on a result will tell you what you have to do to fix the problem. As I was running SQL 2000 sp4, it correctly flagged that I needed to upgrade that to SQL 2005, at this point I exited the SMS>SCCM process (click on cancel) and got my SQL 2005 iso (en_sql_2005_std_x86_dvd.iso).

Step 4. Configure the Windows Deployment Services gui (mmc snap in) Click on Start/All Programs/Administrative tools/Windows Deployment Services. at this point we can see that WDS is not configured yet, so let's do that now. right click on the server name in the left pane and choose Configure Server at the welcome page click next change the remoteinstall path from the default C:\RemoteInstall to D:\RemoteInstall I put a checkmark in each of the DHCP options then clicked next I then chose to respond to all known and unknown computers (by default it's set to Do not respond to any) Please note, if you want to set this option to only respond to known computers, then you can do so, but you will have to prestage your computers in Active Directory to do so clicking on Finish applies these settings when done, you'll be told that the configuration is complete and that you can now add images to the WDS server, click on Finish (again). Step 5. Adding boot.wim and install.wim Note: You should use only the boot.wim file from the Windows Server 2008 DVD. If you use the boot.wim file from the Windows Vista DVD, you will not be able to use the full functionality of Windows Deployment Services for example, multicasting. If you have the Windows Vista SP1 dvd, you can safely use that for the boot.wim. The Windows Deployment Add image wizard will appear, insert your Windows 2008 Server DVD and click Browse, select the sources folder on the Windows 2008 DVD and then click next you'll be prompted to create a new image group, lets call it ImageGroup1 (the default name, you can change it later to Windows Server 2008 or Windows Vista Sp1 or whatever...). review your settings and click next when ready After a long while, the selected images will be added to the WDS server click finish and review the WDS server as it is now in the Boot Images pane, you should see Microsoft Windows Longhorn Setup (x86) and this is the original boot.wim file from the Windows 2008 Server DVD, please note that this is the default description name of the image, you could change it when addint the boot.wim image to something more descriptive as in this example In the Install Images pane, we can see the six available images from the Windows 2008 Server DVD, these are based upon the install.wim file on the DVD. you can now PXE boot your client computers to the Windows 2008 WDS server. troubleshooting note: if you add a new image to WDS and attempt to pxe boot and then install the image but get an error saying something like 'could not display the list of' then make sure you have used BOOT.WIM from a Windows Server 2008 DVD or Windows Vista sp1.

Step 2. Add the DHCP role After completing Step 1, you now should see that Active Directory Domain Services and DNS server are installed (you can verify this in Server Manager, Roles, Roles Summary). Now that we are in server manager lets click on Add roles again followed by next. Select DHCP Server and click next. Review the information about DHCP server... and if you have more than one network card in your Windows 2008 server, select the one which will be handing out ip's (in my case that is 192.168.3.1), I removed the tick from the other network card listed next you will need to clarify which DNS server ip address to listen to, I changed it from my second nic's ip address 192.168.3.1, clicking on Validate will verify that it's ok enter your WINS settings, I went with the default and clicked next, next we have to input our DHCP server scope options, to do this click on Add enter your scope settings (mine are listed below) click ok and your DHCP scope will now be listed click next and you'll get IPV6 options, I chose to disable this as I'm not using IPv6 yet next we are asked about DHCP credentials for the AD DS, I stayed with the default, and then we will see a summary of our actions and choices for the DHCP server role clicking on Install will apply these settings and after some time you should hopefully see the following:- Step 3. Add the WDS role:- In Server Manager, Highlight and select Windows Deployment Services and click next. you will get an information screen which has some info including the following:- Click next and notice the two role services listed, Deployment Server and Transport Server, make sure they are both selected and click next to continue. view the summary and click install to install the WDS role... after some copying you should see this if you check server manager under roles you should now see the WDS role added.

Note: If you already have an Active Directory setup and configured DNS then skip to Step 2 (Setup DHCP). If you have already configured AD, DNS and DHCP then please skip to Step 3 (Add the WDS role). This guide assumes that you have first of all installed Windows 2008 server on your machine and partitioned it as c: (Operating system) and d: (data), note that you can change the partitions after the installation of Windows 2008 server by using disk management and right clicking on a disk and choosing to shrink or extend. This guide is to help you set things up in a LAB. In Production, you have to plan things according to Technet documentation. Step 1. Setup and configure active directory Click on Start and choose Server Manager, scroll down to Roles Summary and choose Add Roles. When the wizard appears click next. As WDS needs the folllowing:- Active Directory Domain Services, DHCP, DNS, we will add the following role first:- Active Directory Domain Services We must install this role first before continuing to add the other roles, so lets select it and click on next. We will then be informed that installing AD requires us to run dcpromo.exe afterwards to make the server a fully functional domain controller. Click install to continue. once done we'll get the success screen click close to continue Once done the server manager will list our ADDS service with a red X beside it, click on it to run Dcpromo.exe. This will open up the Roles section of Server manager, and we'll see a summary which says This server is not yet running as a domain controller. Run the Active Directory Domain Services Installation Wizard (dcpromo.exe). Click on the blue text to continue. This will start the Active Directory Domain Services Installation Wizard. Click on next to continue. Next we will get a screen telling us that older versions of Windows (pre Vista Sp1 ....) may have problems with a bunch of things including Windows Deployment Services (for more info read KB942564) click next to continue Now we get to choose what type of domain we will setup, and for the purpose of this lab, we will select the second option, Create a new domain in a new forest. next we are prompted for the fully qualified domain name of the forest root domain (eg: corp.contoso.com) Note: if you have not already given this server a good computername, then cancel this process and do so now. The computername will be prepended to whatever FQDN you enter, so if you enter corp.contoso.com then the FQDN of this domain controller will be AD1.corp.contoso.com after clicking next the wizard will check the validity of the fqdn, next we get to choose the forest functional level, click the drop down menu and select Windows Server 2008 from the three choices (Windows 2000, Windows Server 2003, Windows Server 2008). As this is only a test lab, we are not concerned that we can only add Windows 2008 or later servers to this forest. Clicking next will give some addtional options, leave them as they are (DNS Server selected) and click on Next again. if you get a warning about dynamically assigned ip addresses ignore it (choose yes), you will most likely get another DNS warning if like me you don't have a Windows DNS server in the forest. Click yes to continue. Next we are asked where to store the AD database, logfiles and sysvol, stay with the defaults and click next. and we are then prompted to set the Directory Services restore mode administrator account password finally we get a summary of our actions click next to get started after a while you should see the AD wizard complete. Click Finish you'll be prompted to restart, so please go ahead and click on Restart Now.

ok what server OS are you using here ? windows 2003 ? and which service pack ? i'll try and replicate this here cheers anyweb

if you've just installed Windows Server 2008, and are trying to get connected to the internet via wireless you'll have no end of problems as it just will not see any wireless networks no matter what driver you install for your wireless card. The reason is because Wireless is disabled by default in Windows Server 2008. To resolve it, do as follows in Server manager scroll down to Features Summary and click on Add Features. When the Select Features window appears, scroll down to Wireless LAN Service, and place a checkmark in there. you'll be informed that the server may need a restart... click install to continue the wireless lan installation service will be initialized and hopefully will succeed click close to continue and then browse your wireless networks as normal choose one to connect to and then you are done ! that's it, cheers niall

ok first of all lets rule out storage as the issue:- have you tried changing the AHCI/SATA mode in bios ? if changing that doesnt help your problem then we need to know exactly how you created your Windows PE image (what boot.wim file did you use and from what DVD (msdn/dell oem vista dvd) please specify cheers anyweb

hi and welcome to the forums are you trying to use WDS to load your optiplex 755's with vista or xp or are you doing something else (capturing/deploying wds images...) on the front of your dell optiplex, does it say VPRO anywhere ?

After being released to manufacturing last week, SP3 for XP is now available as either a standalone installer (direct download link) or at Windows Update. PC Magazine has coverage of the new service pack, including launch details, a hands-on review, slideshows, and expert tips. via osnews.com

Despite Microsoft's obvious focus on selling Windows Vista to its customers, it hasn't yet forgotten about all those people out there that still use Windows XP (personally, I use Windows XP MCE 2005). The company has confirmed it has finally 'released to manufacturing' the third service pack to Windows XP - 7 years after the operating system's original release. via osnews.com microsoft > http://forums.microsoft.com/TechNet/ShowPo...3&SiteID=17

hi Mike, so it's all working now ? this is excellent ! did you use my new WIM file at all ? i'd like to know if you tested it and if it worked. the reason we used the vista drivers was because WDS used the Windows Vista DVD to create the boot.wim file (which gives us windows PE....) and that needed the vista driver not the XP driver. i actually live in Sweden, Europe and i'm happy to talk about this on the phone if you want or on MSN either way i'm glad things are working for you now, spread the word ! cheers anyweb

no that's not enough, you must import the wim into WDS by choosing 'add boot image' in the WDS gui in addition i think we've been using the wrong INF's all along, instead of using the windows xp ones we should be using the vista ones for windows PE.... so i've updated the WIM one last time to include the correct infs (i hope) sorry about this, but as I don't have an Optiplex 755 it's hard for me to test the theory please download this new WIM and test it, i'm very hopeful that it'll work here's what I did to put it together, C:\>"c:\Program Files\Windows AIK\Tools\PETools\copype.cmd" x86 c:\windowspe-x86 C:\windowspe-x86>Imagex /info "D:\remoteinstall\boot\x86\images\windows-noob_capture-(2).WIM" C:\windowspe-x86>Imagex /mountrw D:\remoteinstall\boot\x86\images\windows-noob_c apture-(2).WIM 1 c:\mount C:\windowspe-x86>peimg /inf="C:\dell\drivers\R162323\Vista32\*.inf" c:\mount C:\windowspe-x86>imagex /unmount /commit c:\mount the most important line above is this one C:\windowspe-x86>peimg /inf="C:\dell\drivers\R162323\Vista32\*.inf" c:\mount ok ? cheers anyweb

ok can you confirm thhat you disabled the wim in wds, then imported mine, then re-enabled it then pxe booted the optiplex 755 what happened then ?

Microsoft has finally pumped out Vista service pack one (SP1) in the remaining 31 languages as a manual download via its Windows Update site. Swedish download > http://www.microsoft.com/downloads/details...;displaylang=sv Bulgarian download > http://www.microsoft.com/downloads/details...4a-09146a0ba746 Danish download > http://www.microsoft.com/downloads/details...4a-09146a0ba746

hi Mike, did you get a chance to test it yet ? cheers anyweb

ok i've added the other inf to the wim, and here it is again to test please test it and let me know are we getting anywhere... cheers anyweb

no problem, at least we know which inf doesnt work now, i'll add the other inf and re upload the wim for you to test ok ?

have you tried to import the image into WDS boot images ? (hint, right click and choose add boot image)

hi Mike i've now updated my wim file (the capture wim) with the driver for Dell Optiplex 755, please download it, add it into your WDS boot images and then tell me does it work for you, if it does work, then I will also make these changes to the deploy wim file. Please download the updated WIM from here (121mb in size) For your reference here are the commands I used to add the driver after disabling the WIM in WDS.

hi Mike the driver is correct, please let me try to update my boot.wim with the driver and supply you with that boot.wim file, i'd be very interested to see if that works as soon as i get the time to do this i will (soon) cheers anyweb

does your optiplex have a vpro sticker on the chassis ? if not maybe you need to be using the broadcom driver s can you check that please.. or verify what the nic is called in device manager cheers

the optiplex 755 came in a few different versions (vpro or not) so it could have an intel or broadcom nic, is yours an Optiplex 755 vpro ? what is the nic listed as in the device manager ? what driver did you attempt to update windows PE with ? the vista or xp version ? if i had one i'd test it here but i dont sorry.