I initially installed Windows Server 2012 R2 Standard Evaluation from Microsoft's website because I didn't have the funds at the time to buy the license. When The trial period ended though, I went to Amazon and bought a copy. But, when I put that key in to activate I get an error "that key cannot be used to activate this version of windows". Now I am stuck I spent $600 and I don't know how to get this key to work.
Can anyone provide assistance or advice?
Thank you
Taylor S
I'm having trouble finding this info believe it or not, or i find conflicting reports...
Creating a base Win2012r2 server for deployment. No worries about default user profile here i do everything in GPO i need.
Im done, i open a cmd prompt
sysprep /generalize /oobe /shutdown
The machine shuts off. Now i grab my image.
At which point is 1. a new sid created and 2. the machine named?
One is because I'm curious and never really knew, but i suspect it has to be on the next boot (i.e. after deployed to a machine) otherwise every machine with that image has the same sid.
Two is because it doesn't seem possible to have 2012 OOBE *prompt* for a computer name like in the old days...and yes in my environment prompting is the preferred way (i know it's possible to get real real creative with scripting the computer name in, but i'm looking for quick and dirty prompting)
Thank you..
I should add, i know the sid is removed with the generalize option, which is what it's doing while you see it "generalize" among other things.Hi all,
I've been given the task to separate our AD infrastructure because we plan on outsourcing our IT work. Before so, they would like to separate corporate infrastructure. So I would like some guidance how to do so? What are your suggests? Create a separate Forest/AD infrastructure and create a trust between them? Any comments would be appreciated!
Hello,,
I am trying to filter all the drivers and force them to install for a HP Elite 8300 USDT and it is not working at all. When I remove the filter all the drivers install except the USB3. What gives? Any ideas?
I am using Server 2012 R2, but I am still using Windows 7 boot, do I need to upgrade that to the server 2012 R2 boot.wim for full support?
Hello,
Does anyone know what to do with this error?
Thanks lots
Tania
When i try to install OS on a platform whith an onboard video installation halts on a random phase (Ex.: 20%, 31%...).
Computer doesnt respond to any keys and the screen is filled with "ants" and other artifacts. When i tryed to install a PCI-ex VC the result was the same.
I tried to dissable frame buffer in bios - no change 
Any ideas how to override this?
My test pc is: AMD x2, nForce MB with GF6100 integrated video.
Sorry 4 my English
To anyone with HP servers, question on how you import drivers:
I create a vendor folder (HP), then model (ProLiant DL580 G5) server version ( i.e. Server 2003) and last cpu type (x86 or x64). I import the storage and network drivers for each (But i dont import duplicates), and create a selection profile for the server model. In the make and model of the DB, I do the make and model of the server as reported by wmi, and select "nothing" for the DriverGroup, and for the DriverSelectionProfile, I select the appropriate selection profile. then I rebuild the lite touch wim files, and import them into PXE. yet I still seem to have storage driver problems. I import everything available for the server for storage per HP's driver selection based on just that model of server. Should i not do that?
I know my make and model is working, becasue I have selected applications that are getting chosen during the deployment wizard.
What are you doing diffrent, or am I doing something wrong? Please post your expiriences, thx!
Hi,
My PXE/WDS was working fine :
PXE/WDS Server on the same vlan as DHCP
Workstation on a different VLAN
I changed the VLAN for the workstations, since then I can boot on PXE with no issue but i get a 0x00000001 error.
I don't think it's a driver issue, because it was working well on the former workstation VLAN.
I tried to import the drivers as described here with no luck.
I think this is more of a routing/firewall problem. Any idea on how to investigate this problem ?
Thanks.
R.
Hello,
I am having an issue with WDS capturing. I have an HP Proliant ge8 running server 2012R2 properly configured as my DC / WDS. I added my boot.wim boot file to my bootable images and verified that I could boot to a WinPE image on my test unit. In the WDS config I right clicked and properly created my capture file using the same Boot.wim file listed above and added my NIC driver and my raid driver. These drivers are 64x and so is the unit I am attempting to capture.
I ran sysprep on my target machine and generalized my system then rebooted it to my capture image. It loads the windows icon and then goes to a black screen. I receive the following error on my WDS, in my event logs.
Error 6/12/2015 17:21:05 Deployment-Services-Diagnostics 57347 None
The PXE server processed a request from a client of architecture x86. However there were no boot images installed for this architecture. PXE clients of this architecture will not be able to complete the boot process successfully. To resolve this problem, add at least one boot image for this architecture.
I installed 64x image files, the boot.wim file came from my server 2012R2 DVD. The drivers i added to my package are 64x drivers taken from my image. The server i am attempting to capture a image from is identical to my wds server, same hardware and same architecture.
Do I need to configure a x86 Boot.wim boot file / capture image in order for my 64x machine to be able to capture?
Does anyone have any ideas?
Hello,
I have WDS installed on WS2008R2 and I want to capture image from VMware VM (syspreped WS2008R2) which is configured with SCSI disk.
I'm using W2012R2 capture image but I don't see any volume to capture. This is most likely because of missing driver for SCSI disk (list disk in diskpart does not show any disk).
Does anyone know where to find SCSI x64 driver which I can inject to capture boot image? I found x86 driver in VMware tools but it's not possible to add it to boot image because of different architecture.
Hi all,
I created a tools which generate a personnalized WinPE iso image to install every servers in my company. This boot winpe image use for instance the IP adress of the server to install.
In the startnet.cmd, I insert a line to launch setup.exe with an unttended file. The windows sources are on a network share. The winpe.iso file size is about 400 MB.
For DMZ deployment, I would like to embed Windows 2012R2 sources in the Winpe image.
Using DISM, I openned the winpe.wim, then I copied the Windows sources in the mount point. Then I closed the image and I convert it to ISO. The winpe size is now 6 GB.
But, when I boot a server using this winpe.iso I get an error message saying there isn't enough memory available.
I created a VM until 32 GB of RAM, in BIOS or UEFI mode. But it does not solve this issue.
Do someone could tell me how to get ride of this message ?
What is the winpe size limit ?
Thank you
ML
I am trying to capture a Windows 8.1 Enterprise (with Update) x64 installation using WDS, but the Capture Image fails to load. I used the boot.wim from the Windows Server 2012 R2 (with Update) ISO to create a boot image in WDS and then a capture image from it. After I press F12 and the progress bar finishes the following message appears:
This only happens when I boot the capture image - the original boot image that I imported in WDS boots normally. I also tried with the Windows 8.1 (with Update) boot.wim, but the issue reoccurs. This is a Hyper-V VM on Windows Server 2012. Is this a problem with the recent update?
Hi,
I've installed a WDS service on a win2012r2 on a different serveur than DCHP but same LAN. No 66/67 option on DHCP neither IPHelper (because on the same LAN).
Error PXE-E7B : Missing MFTP server
When looking at the netwok, I can see the DHCP communication but somehow the "DHCP offer" from the WDS offer 0.0.0.0 as the IP address that logicaly, to my opinion, leads to a NAK from the DHCP server, right ? 0.0.0.0 is the client trying to PXE boot 10.180.10.201 is the DHCP (it offers a correct @IP 10.180.103.30) 10.180.10.216 is the WDS (give 0.0.0.0 as @IP...)
And this is where I can't figure out why, any suggestion ?
Regards,
Johann
A server at a remote site has been having some minor performance issues. The main concern was that Java could not be installed which was required for the RAID monitoring software. After some troubleshooting, it was determined that the wrong type of OS was installed and it was running Server 2008 R2 Standard Checked Build (Debug) version. It is primarily using AD, DNS and DHCP roles.
Is it possible to do an in-place upgrade to the regular version of 2008 R2 Std (or 2012/2012 R2) or is a full reinstall required?
I have a software application I want to be installed after deploying Server 2008 R2 (any edition) but it requires .Net Framework 3.0 to be present. If I try to use DISM to enable the feature, it returns an error. This is the command I used:
DISM -IMAGE:c: -ENABLE-FEATURE -FEATURENAME:NetFx3 -SCRATCHDIR:c:\temp
and this is the error I receive:
Error: 0x800f080c
Feature name NetFx3 is unknown.
Using -GET-PACKAGES on the offline image shows NetFx3 is disabled. I tried to search for this already and couldn't find any solutions for 2008 R2.