anyweb

Create a Package from Definition for the ConfigManager Client complete the following Step (step 3). Create distribution point and then update it complete the following Step (step 4) >> continue on to complete the next part

Create a Distribution Point and Update it for the Sysprep Package Expand the Sysprep Package we have just created in ConfigMgr and right click on Distribution Points choose New Distribution Points Click next and select only the standard distribution point (exactly as we did above for the Operating System Install package), click close when done. Once created, right-click on distribution points again and this time choose Update Distribution Points. answer Yes when prompted

Create the XP SP3 sysprep package download the XP SP3 deploy.cab file and extract its' contents (or just the sysyprep.inf file) to a folder called sysprep. Create a network share and copy the contents of the sysprep folder into the share, call the share sysprep. Note: if you are trying to deploy XP SP2 then use this one instead. Note that the Sysprep package will be used in a step called Install Deployment Tools which must happen after Setup Windows and ConfigMgr step but before the Prepare Configmgr Client step, we will be creating the task sequence in the next part and it will automatically insert that step in the correct place, however we need to define the Sysprep Package first. I'd also recommend you copy your unattend.txt file to the sysprep package, we will use this to make changes to our Windows XP image in the Apply Operating System Image step (see below) In ConfigMgr expand the Software Distribution node and right click on Packages and choose New Package. fill in the package details for Data Source, point the wizard to the sysprep share you created earlier eg: \\WIN-AE2V1IRN067\sysprep leave Data Access as it is Leave Distribution Settings as they are for reporting and security just click next, and click next again at the summary and review your actions on the confirmation screen. Note: If you are trying to deal with AHCI drivers via sysprep then please read this post

Create a New Collection In SCCM ConfigMgr, highlight collections, right click and choose New Collection, fill in the collection general details and call this collection Build And Capture XP leave Membership Rules blank click OK to the warning click next on the advertisements and security screens click close when done

Create a Distribution Point for our Install Package expand the Install package we've just created and right click on Distribution Points, choose New Distribution Points click next when the wizard appears and select only the first distribution point, do not select the PXE distribution point as this is not a boot image. click close at the confirmation screen Now the we have created the distribution point for the operating system install package, let's update the distribution point. Right click on Distribution Points and choose Update Distribution Points answer Yes to the confirmation

i'll try and do it this week, watch this space................

sounds like this have you actually configured WDS at all or just configured the dhcp options ? is there a switch between the windows 2008 server and the novell dhcp server ?

hi webuser, if you understand how SCCM works then the following guide should help you give it a try at least and let us know does it work or not, If I have time to do an XP guide I will, but right now I don't.... cheers anyweb

Today, the Windows 7 operating system was announced at PDC. Attendees heard how the forthcoming release can help customers leverage previous investments in the Windows Vista operating system. Enhance security and control. Reduce power consumption. And seamlessly connect their people and devices.

it means you need to install the WAIK do that, and then try again cheers anyweb

ok first of all are you deploying XP or Vista ? and I assume the two computers you are attempting to install to are both 32 bit and 64 bit ? from your error it sounds like WDS is not configured correctly take a look at this post to get an idea of the options cheers anyweb

Edit the Task Sequence Now we need to edit our Task Sequence to add the conditions necessary to selectively install applications/drivers, so expand the Operating system deployment node and expand Task Sequences and select a Task Sequence. Right click on it and choose Edit. When the Task Sequence appears, highlight Setup windows and ConfigMgr and then click on the Add drop down menu click on New Group from the choices when the New Group appears, change it's name to Dell Latitude D430 Adding the WMI Query to detect our Model type Now click on the Options Tab and then click on the Add Condition drop down menu, choose Query WMI Paste the following code in to the WQL Query box SELECT * FROM Win32_ComputerSystem WHERE Model Like "%Latitude D430%" You can even test your query by clicking on the Test Query button (will return 1 if true, 0 if not) Click on Ok and then click on the Properties Tab again. Add the Quickset Application to the Task Sequence click on the Add drop menu again, and choose General then Install Software change the Name from Install software to Quickset and then click on the browse button select the Dell Quickset package from the list ... and click ok then apply and that's it, you can now do a test deployment to see the Dell Quickset application installing itself on Dell Latitude D430's, once you've succeeded in the above you can broaden this further by installing applications like Intel Proset

Identify the hardware name in WMI Now we need to query WMI to find out the hardware name (we'll need it for later). Open a command prompt on your client hardware (the machines you intend to be deploying to....) and type wmic To find out the model name type this CSProduct Get Name The result is what we need Below is a sample output from a Dell Optiplex 745

Distribute the Package and update distribution points Now that we have created our Package and created a program for it, we need to create a distribution point for it and then update that distribution point with the package. Right click on Distribution Points beside our newly created package and select New Distribution Points. click next when the Wizard appears and select the first distribution point (do not select the PXE DP as this is not a boot image....) click next and then close at the summary screen. Now that we've created a Distribution Point let's Update it, right click on our packages Distritbution Points and choose Update Distribution Points answer Yes when prompted

Create a Program ok now that we've created our package above, let's create a program (needed to install the application). Highlight the package, expand it and right-click on Programs, select New, Program. when the wizard appears, type Applications for category type, fill in the other details and click browse make sure to select file type to All files and then highlight quickset.msi and click open then paste in the folllowing line msiexec.exe /i "QuickSet.msi" /qn -silent REBOOT=ReallySuppress and click next, the switches were taken from the README.HTML file provided with this application On the requirements screen we can decide how long this application is allowed to take to install and on what OS types it can be installed on for Environment make sure that whether or not a user is logged on is highlighted from the choices available otherwise this will not work on the Advanced screen, also make sure that Allow this program to be installed from the Install software Task Sequence without being advertised is selected for the Windows Installer and MOM Maintenance screens stay with the defaults, click next at the summary and close at the confirmation

One of the big problems with deploying computers today is getting all drivers installed correctly, some drivers will install just fine using the standard PNP (plug and play) routines within Windows Setup providing of course that you have first added the drivers to driver packages and distributed them to your distribution point(s), some drivers however are not so easy to install and require an application to be run in order for the hardware to function, examples are Bluetooth, Wireless, 3G amonsgt others. These applications contain the drivers needed plus several support files/apps and what not. Therefore you need to have a method of installing applications and in addition you need to be able to target what hardware these applications get installed onto (you don't want wireless drivers being pushed out onto a non-wireless desktop for example. In the example below we will deploy an application called Quickset on a Dell Latitude D430, and I will quide you through the processes needed to get you there. Obviously you can replace the Hardware type with whatever model you are using and in addition you can use whatever application/driver you wish, the purpose of this guide is to show you how to target selected hardware Get the Application download the following file and run it on a test Dell computer, it will decompress the files to c:\dell\drivers\R180762, copy that folder and all files in it to your drivers share on your SCCM server (eg: \\servername\drivers\R180762) Create a Package Ok now that we have the files, and copied them to our SCCM drivers share, we need to create a package in SCCM, so open the Software Distribution node and expand Packages. Right click on Packages and choose New, Package. When the Wizard appears fill in the general details place a checkmark in this package contains source files and click on Set fill in the path to where you copied the driver (a driver share on your SCCM server) and place a checkmark in update distribution points on a schedule this will allow you to update versions of this application by simply copying the files to that folder... click next and leave data access settings as they are set the Distribution Settings to High for sending priority leave reporting and security as default review the summary and verify all green ticks, then click close at the confirmation screen

got this error today just after PXE booting The error had me confused for a bit but after rebooting a few times I eventually noticed that the PXE boot prompted me to press F12 to choose boot (like a normal lite touch or RIS menu) prior to the error, so one time I pressed F12 and it displayed the Windows Boot Manager menu with two choices, Setup Vista or Setupy Windows Server 2008 (my WDS menu basically...) So, why didn't it automatically PXE boot into the Server deployment, the reason was simple, even though I had imported the computers settings into the OSD section of SCCM, I had made a mistake in the MAC address, so it never would 'auto f12' the pc in question and instead, defaulted to prompting me for F12 followed quickly by the error above. solution, type in the correct MAC address ! Once done, it will PXE boot as normal and after verifying the MAC address with the one in SCCM's database will apply pxeboot.n12

ah good to hear it, you can get a lot of WDS info including how to capture and how to deploy images right here in the WDS section if you want semi interactive menus during the wds deployment then lite touch (LTi) is the way to go and you'll need to install MDT for that, if you think it's confusing now just wait till you try SCCM 2007, cheers anyweb

have you tried removing anything between the server and client, ie direct connection to rule out SWITCH or routing issues ? if that doesnt help have you checked your logs and event viewer for clues ? cheers anyweb

have you tried this method ? if that's not what you need then please show me a sample of what you are trying to do (link)

In the Operating System Deployment section of SCCM right click on Computer Association and choose Import Computer Information when the wizard appears select Import Computers using a file The file itself must contain the information we need in this (CSV) format COMPUTERNAME,GUID,MACADDRESS (sample below) if we look at the last line, I've marked the computer name in Red, the GUID in BLUE and the MAC address in GREEN, separate these values with commas as above. w2k8deploy,BFAD6FF2-A04E-6E41-9060-C6FB9EDD4C54,00:03:FF:77:7D:76 the file can be a standard TEXT file that you create in notepad, and you can rename it to CSV for easier importing into our wizard... so, click on Browse and browse to where you've got your CSV file on the Choose Mapping screen, you can select columns and define what to do with that mapping, eg: you could tell it to ignore the GUID value (we won't however) on the next screen you'll see a Data Preview, and this is useful as it will highlight any errors it finds with a red exclamation mark, in the example below a typo meant that it correctly flagged the MAC address as invalid so edit your CSV file again and fix the error, click previous (back) and try again until it looks like this here's a sample file..macguidcomputername.csv Next choose the target collection where you want these computers to end up in review the summary in SCCM collections, we can now see the computers we've just imported from File, thats it ! If you want to script this then read this post on MSDN cheers anyweb

Celebrating 25 years For 25 years, Microsoft Press books have focused on helping you take your skills and knowledge to the next level. Celebrate our 25th Anniversary with a "Free E-Book of the Month" offer! Simply sign up for the Microsoft Press Book Connection Newsletter for notification of offers, register, and download the selection of the month. Windows Server® 2008 TCP/IP Protocols and Services by Joseph Davies ISBN: 9780735624474 Your essential guide to TCP/IP—fully updated for Windows Server 2008 and Windows Vista. For more information or to buy the print version of this title, visit the Microsoft Learning website. View Chapter 1: Local Area Network (LAN) Technologies or Sign up to download the entire e-book (PDF, 21.1 MB).

"Windows 2000 code was 5.0 and then we shipped Windows XP as 5.1, even though it was a major release we didn't' want to change code version numbers to maximize application compatibility." ... "That brings us to Windows Vista, which is 6.0. So we see Windows 7 as our next logical significant release and 7th in the family of Windows releases." ... "So we decided to ship the Windows 7 code as Windows 6.1 - which is what you will see in the actual version of the product in cmd.exe or computer properties." read it all on the E7 blog send me a copy Mike ! cheers anyweb

NAP - What is it ? In simple terms, Network Access Protection is a client server technology for identifying compliant or non-compliant computers and then deciding what level of access they can have to the network (thereby stopping others from getting infected by viruses and such). If you think for example about remote users dialing in from their home pcs using a VPN connection, those computers are not directly controlled by the network administrator, at least not until now, if you enforce NAP then they could be denied access to your network resources until they are compliant. Note: NAP is not designed to protect a private network from malicious users. It is designed to help administrators maintain the system health of the computers on a private network. NAP is used in conjunction with authentication and authorization of network access, such as using IEEE 802.1X for wireless access. NAP does not prevent an authenticated and authorized user with a compliant computer from spreading a malicious program to the private network or engaging in other inappropriate behavior. But who decides the level of compliancy ? that of course is up to the network administrator, they decide upon a health policy which specifies what criteria you must meet in order to be compliant, for example having a certain level of Security patches and Antivirus updates. The health policy can decide 3 ways of interacting with your network, namely:- * If the system is non-compliant, patch it to the required level first before allowing access to the network * If the system is non-compliant, deny or restrict the user/system access until they meet the health policy criteria * If the system is non-compliant let the user/system have access but make a note of their non-compliance in a report (called reporting mode) In order for the 'health' of the client system to be determined there are two requirements that must be met, the client system (Enforcement Client or EC) must have a client component installed and the server must have a corresponding server component. For example, on the client a System Health Agent has the job of assessing the current state of the health of the client, and the server has a corresponding System Health Validator which checks over the report received from the System Health Agent in order to proceed. these two client/server components are reffered to as SHA and SHV. The information that the SHA sends to the SHV is called the Statement of Health (SoH), the SHV then checks this information and validates it to determine if the EC is compliant or not. The SHV then sends back a response to the client system (EC), this response is called the Statement of Health Response or SoHR. Statement of Health Responses (SoHr) are collected from all System Health Validators (SHV) so that a decision can be made about a clients network access, the decision is sent back to the client so that it knows whether it is compliant or non-compliant. What computers support NAP ? On Windows Vista and Windows Server 2008 computers, the Windows NAP agent is built into the operating system, with Windows XP you need Service Pack 3 installed to use the NAP client for XP, however, the NAP Client Configuration console and NAP product help are only available on Windows Vista and Windows Server 2008. Linux users too are supported with a Linux NAP client from Avenda Systems. How does NAP get enforced ? NAP enforcement mechanisms include DHCP, VPN, IPsec, 802.1X and Terminal Services Gateway, you can use one or many depending on your needs and each would require specific setup and configuration so you need to choose wisely. For more details on Network Access Protection mechanisms see the NAP page on Technet. How do I get NAP help ? Client help is available on computers running Windows Server 2008 or Windows Vista by typing the following at the command line:- hh nap.chm Alternatively you could of course open the NAP Client Configuration console and press F1. What is the Network Policy Server ? The Network Policy Server is a Windows Server 2008 computer that has a role called Network Policy Server installed on it. This server has policies configured on it which determine the network access that is allowed to the client depending on it's SoH from the SHA. This network access can only be decided by first configuring policies on the Network Policy Server, the three different policies are called Connection Request Policy (allows network access with at least one condition), Health Policy (identifies which SHV's are being used to determine the health of computers. You will normally setup two Health Policies, one for compliant (health checks pass) and the other for non-compliant (health checks fail) clients. Finally we have Network Policy which determines the level of network access a client will be given (or denied) based on the SHA checks. The policies on the Network Policy server ultimately determine whether non-compliant computers are remediated (patched) or whether they get full or restricted network access, so whoever defines the policies determines how non-compliant computers are treated. When the Network Policy Server is being used with Network Access Protection it is referred to as a NAP health policy server. How can I setup NAP in a test lab environment ? Here are 4 whitepapers from Microsoft detailing how to setup NAP: • Step-by-Step Guide: Demonstrate IPsec NAP Enforcement in a Test Lab • Step By Step Guide: Demonstrate 802.1X NAP Enforcement in a Test Lab • Step-by-Step Guide: Demonstrate VPN NAP Enforcement in a Test Lab • Step-by-Step Guide: Demonstrate DHCP NAP Enforcement in a Test Lab For a NAP Intro written by Microsoft, take a look at the following document.

and here's some info on Unknown computer Support in the R2 release