anyweb

Editing the Task Sequence The Task Sequence is like a list of instructions telling our installer how to install the OS (in this case Windows Server 2008), you will probably want to customise several of the actions in the default task sequence. To modify the task sequence, right click the Server Task Sequence we created in Part 1 and choose edit The task sequence will then be displayed We could choose any of the categories on the left side and view the appropriate options tab on the right pane, Set the Administrator Password In the left pane of the Task Sequence click on the Post Install heading, and select Apply Windows Settings, select Enable the account and specify the local administrator password, enter a strong password and click apply. If you don't do this then you won't be able to logon to the server if something goes wrong.

Import new Task Sequence In the Operating System Deployment node of ConfigMgr, select Task Sequence, right-click and choose Import Microsoft Deployment Task Sequence from the options Note: This guide was written when MDT 2008 was the current version, since then MDT 2010 has been released and Microsoft has reworded Import Microsoft Deployment Task Sequence to Create Microsoft Deployment Task Sequence. when the wizard appears select Server task sequence from the drop down menu and click next, fill in the general details, click next... on the next screen you need to fill in the workgroup or domain joining details (I chose to join the w2k8 domain), plus provide details of a user with that permission, and enter your product key, in addition you must specify the UNC path of where to store the captured WIM file which we will call server2008.wim. eg: \\WIN-AE2V1IRN067\captures\server2008.wim for boot image you can specify which one you require by clicking on the Browse button and selecting the boot.wim file that we created earlier (32 bit boot.wim), Next we will create the MDT server source files package (which will contain all of the scripts and supporting files needed for the Microsoft Deployment Toolkit). In explorer, create an empty folder called MDTserverfiles and share it. fill in the details... on the OS Image screen, choose to Specify an existing OS install package click on the Browse button and select the Server 2008 installation Package we created earlier click next when ready for the client package we can specify the one we created earlier from a predefined package Settings Package next we will create the Settings package (Contains the unattend.xml file used for an automated installation of Windows Server 2008 as well as the customsettings.ini file used with the Microsoft Deployment Toolkit), so create a folder in explorer called MDTserverSettings and share it as MDTserverSettings click on create a new settings package and browse to our network share eg: \\WIN-AE2V1IRN067\MDTserverSettings fill in the descriptive details For the Sysprep Package, choose No Sysprep Files required, and click Next, at this point it will create/update all package and settings we specified. when copying is complete, you can now browse the MDT Server files and MDT Server Settings folders we created and then shared, they are now populated with files and here is where our customisations will be stored... continue to >> Part 2

it's a really strange error you are getting, are you getting the same error for all xp versions you listed in the previous post ? what was different between your test setup and the production server ? cheers anyweb

Do you want a free hypervisor – Now you can download Microsoft Hyper-V Server 2008. Licensing Microsoft Hyper-V Server 2008 Microsoft Hyper-V Server 2008 is a stand-alone product that will be available via the Microsoft Download Center free of charge. Microsoft Hyper-V Server 2008 does not require CALs for the product itself. CALs will be required for all Windows Server virtualized operating systems which are hosted on Microsoft Hyper-V Server 2008. Microsoft Hyper-V Server 2008 will be available in the following languages: English (EN-US) German (DE-DE) Japanese (JA-JP) French (FR-FR) Spanish (ES-ES) Chinese Hong-Kong (ZH-HK) Chinese Simplified (ZH-CN) Korean (KO-KR) Portuguese (Brazil) (PT-BR) Chinese Traditional (ZH-TW) Italian (IT-IT) Russian (RU-RU) When to Use Hyper-V Server 2008 Microsoft Hyper-V Server 2008 is a great choice for customers who want a basic and simplified virtualization solution for consolidating servers as well as for development and test environments. Hyper-V Server 2008 only offers the most basic of virtualization features, making it ideal for: Test and Development Basic Server Consolidation Branch Office Consolidation Hosted Desktop Virtualization (VDI) Customers who require richer and more robust virtualization features, such as Quick Migration, multi-site clustering, large memory support (greater than 32 GB of RAM), and more than four processors on the host server, should use Windows Server 2008. Windows Server 2008 provides business continuity, disaster recovery, greater scalability for consolidating large workloads, and flexible and cost-effective virtualization rights (one free virtual instance for Standard Edition, four free virtual instances for Enterprise Editions, and unlimited virtual instances for Datacenter Edition with the purchase of a license of Windows Server 2008).

User Interface: Managing Windows windows We’ve booted the machine, displayed stuff on the screen, launched programs, so next up we’re going to look at a pretty complex topic that sort of gets to the core role of the graphical user interface—managing windows. Dave Matthews is program manager on the core user experience team who will provide some of the data and insights that are going into engineering Windows 7. --Steven The namesake of the Windows product line is the simple “window” – the UI concept that keeps related pieces information and controls organized on screen. We’ll use this post to share some of the background thinking and “pm philosophy” behind planning an update to this well established UI feature. full story > http://blogs.msdn.com/e7/archive/2008/10/0...ws-windows.aspx

which boot.wim are you using in WDS ? it is the boot.wim file that you need to be adding network drivers to, if you havn't done that then it will not be able to contact the server....

how much ram have you got in the client you are trying to install ? can you give any more details of where the failure occurs please cheers anyweb

this sounds like you dont have correct network driver support for your model in windows PE (needed to install vista) so...... what computer make and model are you working with here and have you checked any of the deployment logs at all ) what network drivers are you currently using ?

1. to decide where the programs go you'll have to modify the program installer directly, usually you'll need to supply some switches to the installer to tell it to install the program somewhere else, checkout this Adobe Reader silent install howto 2. as above read that link as he has some script (install.bat) for deleting the icons that adobe reader places in the AllUsers profile... cheers anyweb

only way to do it is to reinstall and decide the path here what applications are leaving 2 icons ? is it Windows Media Player ?

download and install the Release Candidate for Openoffice 3 then download and install the plugin that’s it now start OpenOffice Draw and edit or create PDF’s, cool ! cheers anyweb

here's a start http://blogs.technet.com/deploymentguys/ar...alkthrough.aspx google is your friend cheers anyweb

start up the Group Policy Management console (GPMC.MSC) and expand the Default Domain policy, right click and choose Edit. when the Group Policy Management Editor appears, expand Computer Configuration/Policies/Administrative templates/Network/Network Connections/Windows Firewall/Domain Profile in the Right pane, double click on the policy called Windows Firewall: Protect all network connections set it to disabled done ! you can now check your domain clients and verify that the policy has taken effect (if you want to speed up things open a cmd prompt on the client and issue gpupdate /force )

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 ?