anyweb

you are not making yourself very clear here, what exactly do you want to do ?

You can use Windows Deployment Services to link physical computers to computer account objects in Active Directory Domain Servers (AD DS). This is called prestaging the client. Prestaged clients are also called known computers. If you have set WDS to only respond to known computers then you'll need to prestage the computers otherwise the PXE boot will fail. To prestage a computer for WDS deployment you'll need to know the mac address or GUID of it, you can get that info in a variety of ways, the easiest (for one computer) is to simply press the PAUSE button on your client pc when it is PXE booting to the server, you'll see both the MAC address and GUID listed. If you want to use scripts to get these values then download the following from Microsoft (Sample_RIS_Scripts.zip), this bunch of scripts can collect GUIDs and more... ok, now that we have the GUID lets start Active Directory Users and Computers, click on Computers and right click, choose New, Computer. give the computer a name click next and make sure to select This is a managed computer Input the GUID or MAC address with no - eg: if the GUID reported in the bios pxe boot screen is then remove the dashes so it reads the Next button below will remain Greyed out (inactive) until you input the GUID (or mac address) correctly select your Remote Installation server (the WDS server....) click next and review the summary, click finish and you have now prestaged your computer in Active Directory. at this point you can PXE boot the client and WDS will treat it as a 'known' computer and you can deploy as per normal. more info about prestaging with WDS from Microsoft here >

it's in the sources folder

if you want to troubleshoot problems in SCCM 2007, you should install this toolkit to make reading/understanding logs easier once installed run Trace32 from the start menu answer yes when prompted Now open a SCCM LOG file (by double clicking on it) and notice how errors appear highlighted in RED

why are you using the autounattend.xml file ? what do you want it to do ? i wonder if the problem you are having is becuase you are using the Dell version, if you remove the PID.TXT file from the dvd do things work ? cheers anyweb

get it here System Requirements: System Center Configuration Manager 2007 SP1 Evaluation (you cannot install this version on a Volume License or MSDN installation).

In SCCM 2007 we have a number of pre-defined Collections such as All Systems, All Users, All Windows XP Systems and so on, however we want to create a new collection to manage our Windows Vista systems. To do this we'll copy an WQL query from a pre-defined collection (All Windows 2000 Professional Systems) and edit it so that it does what we need, start up SCCM configuration Manager console, expand Collections under Computer Management, and select the All Windows 2000 Professional Systems collection, right click on it and choose properties and click on the Membership Rules tab. click the Edit Query Statement icon (looks like a hand holding a document) click on Edit Query Statement and when you are presented with a results screen click on Show Query Language This will display the query, mark it choose Copy. click ok, cancel, cancel.

to keep your Windows Vista activation read this post please

let me get this straight, are you saying that your only problems are 1. that you loose AERO after deployment and 2. that you have to re-activate Vista is this correct ? is this a Dell version of Vista ? cheers anyweb

yes you can do this but take it one step at a time build your vista image (so that you are happy with it) then install the WAIK (on another pc if you wish) and use imageX to make a WIM copy of it once done you can then start to experiment with your autounattend.xml file.. windows SIM (contained in the WAIK) will allow you to build/design the xml file. Microsoft have a detailed guide to doing all of this here cheers anyweb

welcome to the forums !

Step 4. Create and Update Distribution point In SCCM Configuration Manager console, highlight the package we created in Step 1 and right click on it, choose Distribution Points/New Distribution Point. when the welcome to New Distribution Points wizard appears click Next Select your SCCM server from the list and click next review the summary and click close Now we need to Update the distribution point we've just created with our advertisement package so right click on distribution points and choose update distribution points answer yes when prompted To speed up distribution of the Advertisements you may want to initiate the User Policy Retrieval & Evaluation Cycle and the Machine Policy Retrieval & Evaluation Cycle which are in the Actions tab of the Configuration Manager properties in control panel (on your client computers....) Below are some screenshots of Firefox and Office packages being deployed to the sccm client computer New Program Ready (Office) Assigned (firefox) Firefox Next steps How can I target an application to an Active Directory Security Group using SCCM 2007 SP1 ? How can I target an application to specific hardware using SCCM 2007 SP1 ? how can I deploy Windows Vista SP1 using SCCM 2007 SP1 ? how can I deploy Windows XP SP3 using SCCM 2007 SP1 ? how can I deploy Windows Server 2008 using SCCM 2007 SP1 ?

Step 3. Advertise the Package Once a software distribution package has been created, along with programs to tell client computers what to do with the package, you need to advertise the program that you want the clients to run. Advertising the program makes a program available to a specified collection of clients. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Software Distribution / Advertisements, right click on Advertisements and choose New Advertisement. fill in your details for the advertisemet and click on the browse buttons to choose the package/program/collection as nescessary: Note: In the screenshot below, the Firefox Application is going to be Advertised to the All Systems collection and all sub collections, in a LAB environment that is ok but in a production environment you would want to carefully plan what computers (or users) would get the software, you can do that by using this method (recommended). when prompted about distribution points, click yes (we will update the distribution point later) set the advertisement schedule and click on the yellow star to set mandatory settings review the changes review your distribution point settings on a fast or slow lan... customise the interaction by setting the time interval to 15 minutes review the security instance/class rights we will get an Advertisement summary, click on next to finish

Step 2. Create a Program for the package In Configuration Manager console, expand our newly added Mozilla Firefox package and right click on Program, choose New from the list of options fill in the program details (we are using the -ms switch for installing firefox silently, for a list of application silent switches please see this page on MSFN.org choose All X86 Windows Vista and All X86 Windows XP for the program requirements set the environment variables (choose Program can run whether or not the user is logged on) leave the advanced settings as they are our package is not a Windows Installer package so we can ignore this page also place a checkmark in the MOM alert option if the program fails review the program summary and click next to proceed click Close to finish.

This guide assumes you have installed SCCM 2007 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. Step 1. Create the Package In this example we are going to deploy Firefox (Firefox Setup 3.0.1.exe). To make updating versions of Firefox easier (this will be covered later in this guide) we will rename the file from Firefox Setup 3.0.1.exe to Firefox.exe. We then copy that file to d:\sccm_packages\apps\firefox (your path may vary). Startup your Configuration Manager console (gui) and click on Site Database/Computer Management/Software Distribution and then select Packages in the left pane. right click on packages and choose New/package a wizard will begin fill in the package properties as you wish in General For Data Source, place a check in This package contains source files and click on Set to specify the source of the sccm package change the source directory location to Local drive on site server and browse to the path of your Firefox package next click ok and then set the schedule to update the distribution points set your Data Access options (I left them as default) don't make any changes to the packages priority unless you think you really need it to have a higher priority, if that is the case then you could set the priority for the package in distribution settings to high keep the MIF properties as default set the Security rights for the package class and instance rights review the summary of choices you made and click next to install the package, you'll then see a confirmation that it's installed

hi again, please read this post first to get an idea of whether your values above are correct or not, the post references a different precision model, that does not matter, use the logic in the post ! when you try the bdd install apart from not seeing your raid array do you get any specific error ? from looking at your provided files i think you may have specified the wrong file name or should be remming stuff out as before read this first to get an idea of how to determine the best way forward

hi and welcome what model computer are you attempting to install XP on ? cheers anyweb

If you are using a virtual pc environment (eg Microsoft Virtual PC 2007) and try to add an install image in WDS you may see the following error Verify if you have mounted the ISO (the Vista Installation DVD) in daemon tools, if so this may be the cause of your problem. Workaround 1. To resolve this error, simply copy the Install.wim file stored in your sources folder on the DVD (or mounted ISO) to a local directory on your virtual pc and retry the WDS add new image wizard and this time substitute the local path for the install.wim file in the wizard instead of the mounted ISO path. Workaround 2. Unmount the ISO in Daemon tolls, and then mount the iso in Microsoft Virtual PC directly by clicking on CD, then Capture ISO image This appears to be something to do with the way Microsoft queries cdrom.sys (in relation to Daemon tools at least....). cheers anyweb

if you havn't tried it yet, then get downloading Google chrome really is cool, with plenty of new features to keep you using it the recently accessed websites graphical thumbnails alone is really cool cheers anyweb

The IE team at Microsoft has released the 2nd beta Internet Explorer 8. Contrary to the first beta, which was aimed at developers, this one one is aimed at normal people like you and me. The list of new features and changes is decent, all focused around three themes (marketing alert): "We focused our work around three themes: everyday browsing (the things that real people do all the time), safety (the term most people use for what we've called 'trustworthy' in previous posts), and the platform (the focus of Beta 1, how developers around the world will build the next billion web pages and the next waves of great services)." Go get it. via osnews.com

hi all, quick FAQ 1. what is this ? it's a gmail account with a difference, instead of yourname@gmail.com you'll get yourname@windows-noob.com 2. how do I sign up ? contact admin@windows-noob.com with the following info desired username= firstname= lastname= 3. how do I access it ? Once you have been provided with the temporary password to login, please go to http://mail.windows-noob.com and login ! feel free to test this by emailing ME with your new email account and the subject 'testing email@windows-noob.com' cheers anyweb

hi and welcome take a look at this i'm still trying to find out about how sysprep reacts with office 2007 though.....

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. Step 1. Configure Client Agents open the SCCM administrator console and expand the site Management/site name/site settings, then select the Client Agents as below: Double click on hardware Inventory client Agent on the right side and verify that it is enabled. Set the inventory schedule to 1 day (This is a LAB after all, in production you might want to use something less intensive, the default is 7 days). Click ok to close. For the Software Inventory agent, verify the schedule is set to 7 days. Click on the inventory collection tab, and delete the default scan listed. Click on the yellow star and add files of type *.exe then click on Set beside location, select Variable or Path name and enter %ProgramFiles%\ as the program path location so that it only scans that area for EXE files, Make sure to remove the tick from the windows directory Next you can enable the Advertised programs client agent , and under the General tab, verify that Enable software distribution to clients is enabled and select New Program notification icon opens Add or Remove Programs as per below screenshot. Note: In the R2 release of ConfigMgr you will have an additional choice called Allow virtual application package advertisement Now click on the notification tab and set it accordingly Next we will configure the Computer Client Agent properties, Failure to configure this correctly or failure to configure it will lead to a failure in Operating system deployment with problems such as this one for Network Access Account we need to enter an account to be used by Configuration Manager 2007 client computers to communicate with network resources. We can use the SMSread account we created earlier (in Step 3 of this guide). Note: Be careful about what account you use as the Network Access Account, you should specify an account that has the minimum rights required, typically just enough to connect to your distribution point shares. It should never have domain admin rights. To see why, read this post. fill in the text you want displayed to your users in the Customization tab leave the reminders tab as it is and then set our BITS settings like this, if you don't want any BITS throttling enabled, then select Not Configured. Also worth checking if you have any BITS Group Policies enabled as Group Policies will override any throttling settings you define here. Check with your AD Network Team responsible for GPO's. click apply and ok. Set our Desired Configuration Management Agent schedule to 1 day Let's leave Mobile device client agent settings as they are for now, and for Remote Tools client agent, set it as follows add some permitted viewers (blank by default) set your remote assistance settings to full control for both solicited and unsolicited remote assistance We will leave Network Access Protection, Software Metering and Software updates Client agent as they are for now.

This guide assumes you have installed SCCM 2007 SP1 and then configured it as outlined here in Part 1. Note: if you are using Server 2008 R2 and need to configure WebDav as below then please read this post first. Step 1. We need to configure the Distribution Point (DP) and the Management Point (MP). Technet: How to Configure the Default Management Point for a Site Open up the SCCM Configuration Manager Console, and highlight the SCCM server listed under site systems, in the right pane we'll see the role's we've already installed. then double click on ConfigMgr distribution point and place a checkmark in Allow clients to transfer content from this distribution point using BITS,... Once done, click ok and Double click on Configmgr Management Point to bring up its' properties. If you are planning on managing mobile devices (phones) put a checkmark in Allow devices to use this management point and click Apply, otherwise don't (it allows anonymous access so Mobile Devices can talk to the Management Point). At this point I checked my SCCM status (click System Status in the left pane, expand it, and choose Site Status, then your SCCM site code, then Component Status), this revealed there were problems with my Management Point which were preventing it from starting. right-click on the Critical error, and choose Show Messages, All. hidden inside one of the two re-occuring errors was this (you have to scroll in the error window to read it) well, i know that Webdav is installed, but perhaps a slight configuration change is needed, so let's start up Server Manager and click on roles then select Web Server IIS and then Internet Information Services (IIS) Manager, then select your website listed under Sites (probably called Default Web Site unless you changed it). In the right side select WebDav Authoring Rules Double click on WebDav authoring rules and you should see the rule you originally setup, click on Webdav Settings in the right pane. so according to the error message above we need to verify the following:- Solution: Make sure WebDAV is installed and enabled. [it is] Make sure there is an authoring rule that allow "All users" read access to "All content". [this rule is not setup yet] Make sure the WebDAV settings "Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true" [they are currently set to false] and "Allow Custom Properties" is set to false.[it's set to true] Ok, let's fix these WebDav problems Note: if you are using Server 2008 R2 and need to configure WebDav as below then please read this post first. Lets start with adding a new authoring rule. In WebDav settings, click on WebDav Authoring rules in the right pane Next click on Add authoring rule under actions and make the changes as per below screenshot, click ok when done and you'll see your new authoring rule listed in Webdav. Click on WebDav Settings now make the changes above ("Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true", and "Allow Custom Properties" is set to false.) Click Apply in the actions pane. lastly you should change the WebDav Behaviour for Allow hidden files to be listed from False to True if this is going to be a Distribution Point using BITS (it is). Note: if you are trying to Configure WebDav in Server 2008 R2 then please read this post. Ok back in SCCM Configuration Manager console, under site status, right click on your SITE and choose Reset Counts, then All. Pressing F5 (refresh) on your keyboard should refresh the system status. A quick look back in System Status for our Management Point, now we can see that it has installed and started properly (to speed up the automatic installation of this, you can use ConfigMgr's Service manager and select the SMS_Site_Component_manager server and restart the service.) If after making the changes above the Management Point role is still complaining about webdav then check the following file in c:\windows\system32\inetsrv\config\schema\WEBDAV_schema.xml (open a command prompt with Run As Administrator to edit the file in notepad). Verify the settings have been applied to this file (even if they are present in the Internet Information services gui), if they are missing, correct them and try again.

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. In a production environment please consult Technet for best practise, see below links: Configuration: Checklist for Required Post Setup Configuration Tasks 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 ----------------------------------------------- This guide assumes you have first installed SCCM 2007 SP1. I would recommend that you do the Firefox application deployment test after completing these 3 parts, and then go through the Deploy Vista guide even if you are only going to Deploy Windows XP.