Balthier

Are there any things that one need to consider when installing the client on the primary site server, or can you just run ccmsetup.exe and let it run its course?

I'm trying to upgrade Server 2008R2 from standard to Enterprise, I run the following command dism /online /set-edition:ServerEnterprise /productkey:489j6-vhdmp-x63pk-3k798-cpx3y /norestart Everything goes fine until "Starting to apply edition-specific settings..." Then I receive the following error, Error:0x80220001 An error occured while applying target edition component settings. Has anyone experienced this issue before?

Hello, I have a Task Sequence, which has only one image, which is for Server 2008R2 standard. MDT has been integrated with SCCM, and before starting the TS, one can select which version of Server 2008R2 one would like to install. If you select Enterprise, it runs the following script at the end Dism /online /Set-Edition:ServerEnterprise /productKey:KMSProductKey But the script fails and gives following error error:1605 The specified product key is not valid for the target edition. Run this command again with a product key specific to the target edition. The Product key is vaild, because it has been verified by MS. The only way I can make the TS not fail, is by inserting the KMS client setup key for R2 Enterprise, instead of the KMSProductKey we have. The KMS client setup key for R2 is Windows Server 2008 R2 Enterprise 489J6-VHDMP-X63PK-3K798-CPX3Y Has anyone else experienced the same issue?

Its not a physical machine, both are Hyper-V guest machines. Server01 is an all in one server Client02 is the client I have not attached any drivers, because I have tried to run this task sequence before, but it failed at the same stage as it is failing now, so I figured it might have something to do with wrong drivers being added to the boot image, so I removed all drivers. If I try to boot the machine after the TS has failed, I get the following error message BOOTMGR is missing. So apparently it has not installed the OS properly, before it fails. I created the OS install package during the Create Microsoft Deployment Task Sequence Wizard (I have integrated MDT2010 with SCCM), but even then it would stop at the same point. So now I am trying to run just a generic SCCM TS, without involving MDT. Should I add the Hyper-V drivers?

My keyboard layout while inserting the password for the Network Access Account is not US, while the Keyboard layout for the WinPE in the Task Sequence is US. Could that cause the Network Access account to fail? Because when I tried to connect to Server01 (which is my All in One server) I received an error I wrote net use u: \\server01\images$ The error I received The password is invalid for \\server01\images$ Then I had to enter credentials, user name first, and password afterwards. At the end I was able to connect to SERVER01 and upload smsts.log (which was in C:\_smsTaskSequence\Logs" Here is its content http://s22.postimg.org/omsf2h8a9/image.png Can't say it tells me much at the moment.

My network access account is set as Administrator, so that should be fine. I'll try to check the log this time, just have to wait for the TS to fail first (my lab computer is quite slow, an old Dell T105). Thanks for your input so far, really appreciate it.

Yes it has been distributed. Where can I find the smsts.log?

Well I tried changing to FQDN and x86 boot image, former gave the same result as earlier, while the latter had it stop at an earlier stage (Apply OS stage).

Yes, the selectd configMgr client package in the TS is the one I crated. If I am going to deploy an x64 Win7 image, shouldn't I then select the x64 boot.wim? Btw, which log file can I take a look at, to see why and where it stopped?

I do provide a product key (I have just not included that in the picture posted about), and the Task Sequence always stops at the Setup Windows and ConfigMgr part.

Hello guys, I am not able to run a Build and Capture Task sequence successfully. There are no drivers included, and I use the boot image called Boot Image (x64) version 6.1.7600.16385 I am running Sccm2007SP2 with R3 installed. Here is what I do step by step 1. Create a package for the SCCM client (I select the default options unless otherwise stated) Then I create a Task Sequence Then I advertise the task sequence, and pxe boot a computer (I am using Hyper-V). After a while the task sequence stops with the following error Where do I go wrong? Which log files can I check?

I'm having PXE problems myself. Sometimes it works, sometimes it doesn't. You could try this and see if it helps http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx You can also have a look here http://netsaber.wordpress.com/2008/07/15/configmgr-os-deployment-wds-and-dhcp-on-same-server-issueresolution/ Btw, when you have installed WDS, DHCP and PXE on the same server, what configuration changes do you make? Why have you set the two DHCP server options 66 and 67 manually?

This brings me to my first question. Since I have installed PXE, WDS and DHCP on the same server, I need to configure said roles, because at the moment WDS service is not started which gives errors on PXE in site status systems. Are my assumptions correct, if I make the following configurations 1. In regedit navigate to following key HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSPXE - Set UseDHCPPorts value to 0 2. Run following commands - wdsutil /initialize-server /reminst:D:\RemoteInstall - wdsutil /usedhcpports:no /dhcpport60:yes This will start the WDS service, and thus start the PXE service. Or is this the wrong solution (when you run WDS, PXE and DHCP on same server)?

Further Configuration of SCCM - In Computer Client Agent, set up sccmadmin as network access account - Set up Client Push installation properties - Enable AD System Discovery, and set Location as Contoso.com domain - Create NO_SMS_ON_DRIVE.SMS on the root of C:\, set Software Distribution, Location of Packages to D:\ Add Roles in SCCM - Server Locator Point - Use Site DB, and this computer's account - State Migration Pouint - Folder is D:\sccmshares\USMT PXE Service Point - Allow PXE point to respond - Enable Unknown Computer request - Respond on all network interfaces, Delay is 0 - Use this computer's account and self signed certificate

Thank you for the feedback. I have read the guides, and thats whats gotten me this far. But I am still struggling somewhat, so I thought it might be easier to help me troubleshoot, if I create a thread where I describe the whole process. I hope that is ok. And yes, I am using SP2. I'm using SP1 for Server 2008 R2, which I assume is the one and only SP for Server 2008 R2? Configuration of SQL Server - Enable named pipes, restart SQL Server and SQL Agent services Creation folders to hold data before data/packages are copied to the DP - Create SccmShares under D: - Create Packages, Images, USMT, Drivers under D:\SccmShares Share said folders - Packages$ : Share permissions Server01-FC, sccmadmin-Change - Images$ : Share permissions Everyone-change, NTFS permissions sccmadmin-modify - USMT$ : Share permissions Everyone-change, NTFS permissions Everyone-modify - DRivers$ : Share permissions Everyone-change