I'm trying to install Windows Server 2008 R 2 (64 bit) on a Dell Laptop.

I downloaded evaluation version of Windows Server 2008 R 2 ISO image from MS site and I burned it to a DVD using burn image feature of windows 8 (right click on ISO file and choose burn image)

In order to boot my laptop from this DVD  I changed BIOS mode from UEFI to Legacy and changed the boot sequence to try first from DVD. When I save changes and do a restart, I get a message saying "no boot device found". I also tried with another DVD where extracted version of ISO image is burned, same result.

Can someone please help me here?

I have been working on setting up a WDS server for awhile now I've got just about everything working the way it needs to except the unattend answer file that applies to the image I'm deploying.  I have followed many walkthroughs but nothing has worked so far. I can get the WDS client windows answer file to apply just fine so I don't have to do anything until the image is installed. 

I finally found that I can apply the unattend.xml file during the sysprep process and it works beautifully through that way. That would lead me to believe the answer file is set up correctly. 

I add the exact same answer file to my image through the wds by right clicking on my image I want to deploy, select properties, clicking the check box to allow image to install in unattended mode and then I select the appropriate file.  When I try to deploy that image it doesn't apply it at all, and I get no errors.

It doesn't seem that there are very many steps to apply the answer file so not very many things should be able to go wrong.

The WDS server is server 2012 and I'm trying to deploy a win7 image both 64 bit.

I have been working on setting up a WDS server for awhile now I've got just about everything working the way it needs to except the unattend answer file that applies to the image I'm deploying.  I have followed many walkthroughs but nothing has worked so far. I can get the WDS client windows answer file to apply just fine so I don't have to do anything until the image is installed. 

I finally found that I can apply the unattend.xml file during the sysprep process and it works beautifully through that way. That would lead me to believe the answer file is set up correctly. 

I add the exact same answer file to my image through the wds by right clicking on my image I want to deploy, select properties, clicking the check box to allow image to install in unattended mode and then I select the appropriate file.  When I try to deploy that image it doesn't apply it at all, and I get no errors.

It doesn't seem that there are very many steps to apply the answer file so not very many things should be able to go wrong.

The WDS server is server 2012 and I'm trying to deploy a win7 image both 64 bit.

I used MDT 2012 for deployment of Windows 7 for several years. Now I am in a new company, set up MDT 2013/ADK to deploy Windows 7. I would like to say " MDT 2013 is rubbish for Windows 7". mayb it's perfect for Windows 8/10. I usually get failed to join domain with error " The account *may* already exist in a different OU " in MDT process. Checked the logs, error is 0x54b, which means no such domain. It's bullshit, I can join domain manually any time. AND, sometimes can join domain successfully.

I think it should be a bug of MDT 2013. Will go back to MDT 2012.

--------------------------

54:484 NetpDoDomainJoin
07/08/2015 17:52:54:484 NetpMachineValidToJoin: 'MDT-4'
07/08/2015 17:52:54:484  OS Version: 6.1
07/08/2015 17:52:54:484  Build number: 7601 (7601.win7sp1_gdr.130828-1532)
07/08/2015 17:52:54:484  ServicePack: Service Pack 1
07/08/2015 17:52:54:500  SKU: Windows 7 Professional
07/08/2015 17:52:54:500 NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0
07/08/2015 17:52:54:500 NetpGetLsaPrimaryDomain: status: 0x0
07/08/2015 17:52:54:500 NetpMachineValidToJoin: status: 0x0
07/08/2015 17:52:54:500 NetpJoinDomain
07/08/2015 17:52:54:500  Machine: MDT-4
07/08/2015 17:52:54:500  Domain: domain
07/08/2015 17:52:54:500  MachineAccountOU: OU=CorpComputer,OU=City,OU=Desktops,DC=domain
07/08/2015 17:52:54:500  Account: domain\April
07/08/2015 17:52:54:500  Options: 0x3
07/08/2015 17:52:54:500 NetpLoadParameters: loading registry parameters...
07/08/2015 17:52:54:500 NetpLoadParameters: DNSNameResolutionRequired not found, defaulting to '1' 0x2
07/08/2015 17:52:54:500 NetpLoadParameters: DomainCompatibilityMode not found, defaulting to '0' 0x2
07/08/2015 17:52:54:500 NetpLoadParameters: status: 0x2
07/08/2015 17:52:54:500 NetpValidateName: checking to see if 'domain' is valid as type 3 name
07/08/2015 17:53:09:507 NetpCheckDomainNameIsValid for domain returned 0x54b, last error is 0x0
07/08/2015 17:53:09:507 NetpCheckDomainNameIsValid [ Exists ] for 'domain' returned 0x54b
07/08/2015 17:53:09:507 NetpJoinDomainOnDs: Domain name is invalid, NetpValidateName returned: 0x54b
07/08/2015 17:53:09:507 NetpJoinDomainOnDs: Function exits with status of: 0x54b
07/08/2015 17:53:09:507 NetpDoDomainJoin: status: 0x54b
07/08/2015 17:53:09:523 ---------------------------------------------------------

Hi,

I am deploying a VHD on a SD card to boot a WIndows 2012 R2 server. I followed this procedure:http://technet.microsoft.com/en-us/library/ee731893(WS.10).aspx

When I boot my VHD I get an error "\Windows\system32\winload.exe" Status 0xc000000e. When I then boot on the repair I notice that the bcdboot command created a second entry in the boot manager with my correct values. But there is also a {default} profile without a partition value in the osdevice parameter. As the {default} profile is assigned to boot per default, it generates this error.

I can resolve this by removing the default entry in the repair on the booted VHD with BCDEDIT. But I would like do prevent this or correct it in my VHD file before it is started. I don't see any way to do so. 

Thank you for your help!

Note: for some reason this behavior changed because I already deployed a server like this about a year ago with exactly the same procedure and then I didn't had the error. The only difference I can think of is the version of Assessment and Deployment Kit I now use (Windows 8.1).

Reaching out to all of you for an answer to a question I am having problems finding the answer to.  Perhaps someone here has had experience in a similar situation.  So here it is.

We are wanting to stand up an enterprise root certificate authority in or organization.  A simple single forest/domain that has its roots in the days of NT4 and therefore is a top level domain.  All DC's are 2008R2 and operating at that functional level.  Anyone here have any experience with standing up a root certificate authority in a top level domain and if so what, if any, catch 22's should I be looking out for?

Thanks for your help!

Hello:

I have a hard time believing that no one else has reported this, but am unable to find an answer. The net effect is that we are unable to set an x64 boot image for our x64 BIOS clients. The settings work for EFI but not BIOS. I have confirmed that the settings are correct with wdsutil and being applied to \RemoteInstall\Tmp\x64{guid}.bcd. However, the default image in \RemoteInstall\Tmp\x86x64{guid}.bcd is the default x86 image not the default x64 image. I don't see an option to change the behavior besides disabling showing both architecture images for x64, which will not meet our needs. For reference I am putting out put of wdsutil show config and bcdedit enum for the relevant BCDs below.

Thank you to anyone who has an idea on how we can fix this behavior.

~joe

############### wdsutil /get-server /show:config  ##########################

Windows Deployment Services Management Utility [Version 6.3.9600.16384]
© 2013 Microsoft Corporation. All rights reserved.

SETUP INFORMATION FOR SERVER
[-----------------------------------------------------------------------------]

Server State:
     OS version: 6.3
     WDS operational mode: Native
     Standalone configuration: Yes

Installation State:
     RemoteInstall location: R:\RemoteInstall
     RemoteInstall share up-to-date: Yes
     Boot files installed:
         x86     - Yes
         x64     - Yes
         ia64    - No
         arm     - Yes
         x86uefi - Yes
         x64uefi  - Yes

[-----------------------------------------------------------------------------]

CONFIGURATION INFORMATION FOR SERVER
[-----------------------------------------------------------------------------]

Server Authorization:
     Authorization state: <Unavailable in standalone configuration>

Answer Policy:
     Answer clients: Yes
     Answer only known clients: No
     Response delay: 1 seconds

Directory Use Policy:
     Prestage devices using MAC: No
     New computer naming policy: %61Username%#
     New computers join domain: Yes

New Computer OU:
     OU type: Custom
     OU:

DHCP Configuration:
     DHCP service status: Not Installed
     DHCP option 60 configured: <Not Applicable>

PXE Bind Policy:
     Use DHCP ports: Yes
     Rogue detection: Disabled
     RPC port: 5040

Interface Bind Policy:
     Policy: Exclude Registered
     Registered interfaces:
         IP => 10.23.88.19

Boot Program Policy:
     Known client PXE prompt policy: NoPrompt
     New client PXE prompt policy: NoPrompt
     Allow N12 for new clients: <Not Applicable>
     Reset boot program: Disabled
     Default boot programs:
         x86     - boot\x86\grub32.com
         x64     - boot\x64\grub64.com
         ia64    - boot\ia64\bootmgfw.efi
         arm     - boot\arm\bootmgfw.efi
         x86uefi - boot\x86\grubia32.efi
         x64uefi  - boot\x64\grubx64.efi
     Default N12 boot programs:
         x86     - boot\x86\grub32.com
         x64     - boot\x64\grub64.com
         ia64    - boot\ia64\bootmgfw.efi
         arm     - boot\arm\bootmgfw.efi
         x86uefi - boot\x86\grubia32.efi
         x64uefi  - boot\x64\grubx64.efi

Banned GUIDs list:

Boot Image Policy:
     Default image type for x64 clients: Both
     Default boot images:
         x86     - Boot\x86\Images\x86_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24.wim
         x64     - Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24.wim
         ia64    -
         arm     -
         x86uefi - Boot\x86\Images\x86_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24.wim
         x64uefi  - Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24.wim

Driver Policy:
     Avoid duplicate driver packages: Yes

WDS Client Policy:
     Logging policy:
         Enabled: Yes
         Logging level: Warnings

     Unattend policy:
         Enabled: No
         Command-line precedence: No
         WDS unattend files:
             x86     -
             x64     -
             ia64    -
             arm     -
             x86uefi -
             x64uefi  -

Server Automatic Refresh Policy:
     Refresh period: 900 seconds

BCD Refresh Policy:
     Enabled: No
     Refresh period: 60 minutes

Pending Device Policy:
     Policy: Disabled
     Poll interval: 10 seconds
     Max retry count: 2160 times
     Message to pending clients:
     Retention period:
         Approved devices: 30 days
         Other devices: 1 days
     Defaults for x86:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for x64:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for ia64:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for arm:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for x86uefi:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Join Only
         Join domain: Yes
     Defaults for x64uefi:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Join Only
         Join domain: Yes

WDS PXE Providers:
     Name: WDSDCPXE
     Path: C:\Windows\system32\wdsdcpxe.dll
     Order: 1
     Critical: No

WDS Device Controllers:
     Name: WDSADDC
     CLSID: {1F05CFEA-D4E4-4049-9C76-7B4F0013ECC9}
     Priority: 32768
     Enabled: No

     Name: WDSSDC
     CLSID: {17FD4B68-06B7-48EB-97B7-1575A171AED9}
     Priority: 32768
     Enabled: Yes

WDS Transport Server Policy:
     IPv4 source: Range
         Start address: 239.192.0.2
         End address: 239.192.0.254
     IPv6 source: Range
         Start address: FF15::1:1
         End address: FF15::1:FF
     UDP Port Policy: Dynamic
         Start port: <Not Applicable>
         End port: <Not Applicable>
     Network profile: <Not Applicable>
     TFTP Properties:
         Maximum block size: 0
         Variable window extension enabled: Yes
     Multicast session policy:
         Slow client handling policy: None
         AutoDisconnect threshold: 256 KBps
         Multistream stream count: 2
         Slow client fallback: Yes
     Multicast Content Providers:
         Name: WDS
         Description: Default Content Provider
         File path: C:\Windows\system32\wdscp.dll
         Initialization routine: WdsTransportProviderInit

[-----------------------------------------------------------------------------]

The command completed successfully.

################# bcdedit /enum /v /store:x64{guid}.bcd ############################

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
fontpath                \boot\fonts
inherit                 {4636856e-540f-4170-a130-a84776f4c654}
nointegritychecks       Yes
default                 {e8bb16a3-4dfe-4ae2-9f97-7c4bb87dcc67}
displayorder            {fe1007b2-0523-416d-9d50-33298712115f}
                        {69a2f1a2-f132-41a0-8861-d0d5cffcb045}
                        {fd14773a-e55c-47e2-82d5-a4d9d23d3c52}
                        {e8bb16a3-4dfe-4ae2-9f97-7c4bb87dcc67}
                        {a5e90e93-5616-4b03-b2a7-d5432d57d6f0}
timeout                 30

Windows Boot Loader
-------------------
identifier              {fe1007b2-0523-416d-9d50-33298712115f}
device                  ramdisk=[boot]\Boot\x64\Images\x64 ADS3 Integration FirstBuild 2014-07-02.wim,{52aa0ff7-f4e7-49b2-baab-a11f4f89347a}
description             x64 ADS3 Developer FirstBuild 2014-07-02
osdevice                ramdisk=[boot]\Boot\x64\Images\x64 ADS3 Integration FirstBuild 2014-07-02.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {69a2f1a2-f132-41a0-8861-d0d5cffcb045}
device                  ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh11.5.1_2014-03-24.wim,{5dd4420c-c86c-4363-994d-18c8e65dfde2}
description             x64_ADS2_Test_PE4-Gh11.5.1_2014-03-24
osdevice                ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh11.5.1_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {fd14773a-e55c-47e2-82d5-a4d9d23d3c52}
device                  ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.4570_2014-03-24.wim,{fb87959c-ff53-4415-8ea4-ce4843bdd1dc}
description             x64_ADS2_Test_PE4-Gh12.0.0.4570_2014-03-24
osdevice                ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.4570_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {e8bb16a3-4dfe-4ae2-9f97-7c4bb87dcc67}
device                  ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24.wim,{817e4a23-df42-4abb-9f8e-0ad2f00ce75c}
description             x64_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24
osdevice                ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {a5e90e93-5616-4b03-b2a7-d5432d57d6f0}
device                  ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.5560_2014-03-24.wim,{16467a12-6ed1-4475-aaf5-2524ad038b7e}
description             x64_ADS2_Test_PE4-Gh12.0.0.5560_2014-03-24
osdevice                ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.5560_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

##################### bcdedit /enum /v /store:x86x64{guid}.bcd ########################

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
fontpath                \boot\fonts
inherit                 {4636856e-540f-4170-a130-a84776f4c654}
nointegritychecks       Yes
default                 {9f89c1b6-303e-463c-b602-bea3b5cd11ac}
displayorder            {231df1e6-3b07-465d-aaad-546ca3615754}
                        {fe1007b2-0523-416d-9d50-33298712115f}
                        {3e10c380-915b-4441-8bd4-b9095db66fe1}
                        {6605b6d7-3bd8-42d1-b8a3-d900c43054f6}
                        {9f89c1b6-303e-463c-b602-bea3b5cd11ac}
                        {69a2f1a2-f132-41a0-8861-d0d5cffcb045}
                        {fd14773a-e55c-47e2-82d5-a4d9d23d3c52}
                        {e8bb16a3-4dfe-4ae2-9f97-7c4bb87dcc67}
                        {a5e90e93-5616-4b03-b2a7-d5432d57d6f0}
timeout                 30

Windows Boot Loader
-------------------
identifier              {231df1e6-3b07-465d-aaad-546ca3615754}
device                  ramdisk=[boot]\Boot\x86\Images\x86 ADS3 Integration FirstBuild 2014-07-02.wim,{3f0fdcdf-f9d8-4bb3-9ee4-23f779d1573e}
description             x86 ADS3 Developer FirstBuild 2014-07-02
osdevice                ramdisk=[boot]\Boot\x86\Images\x86 ADS3 Integration FirstBuild 2014-07-02.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {fe1007b2-0523-416d-9d50-33298712115f}
device                  ramdisk=[boot]\Boot\x64\Images\x64 ADS3 Integration FirstBuild 2014-07-02.wim,{52aa0ff7-f4e7-49b2-baab-a11f4f89347a}
description             x64 ADS3 Developer FirstBuild 2014-07-02
osdevice                ramdisk=[boot]\Boot\x64\Images\x64 ADS3 Integration FirstBuild 2014-07-02.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {3e10c380-915b-4441-8bd4-b9095db66fe1}
device                  ramdisk=[boot]\Boot\x86\Images\x86_ADS2_Test_PE4-Gh11.5.1_2014-03-24.wim,{54b01cf1-554f-4511-ba0a-ec3aa7546ca3}
description             x86_ADS2_Test_PE4-Gh11.5.1_2014-03-24
osdevice                ramdisk=[boot]\Boot\x86\Images\x86_ADS2_Test_PE4-Gh11.5.1_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {6605b6d7-3bd8-42d1-b8a3-d900c43054f6}
device                  ramdisk=[boot]\Boot\x86\Images\x86_ADS2_Test_PE4-Gh12.0.0.4570_2014-03-24.wim,{4cd3351c-a8b3-4835-b0b8-b3d475aae2e2}
description             x86_ADS2_Test_PE4-Gh12.0.0.4570_2014-03-24
osdevice                ramdisk=[boot]\Boot\x86\Images\x86_ADS2_Test_PE4-Gh12.0.0.4570_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {9f89c1b6-303e-463c-b602-bea3b5cd11ac}
device                  ramdisk=[boot]\Boot\x86\Images\x86_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24.wim,{91fa1a8e-fee5-407b-aaa6-c5e20d787932}
description             x86_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24
osdevice                ramdisk=[boot]\Boot\x86\Images\x86_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {69a2f1a2-f132-41a0-8861-d0d5cffcb045}
device                  ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh11.5.1_2014-03-24.wim,{5dd4420c-c86c-4363-994d-18c8e65dfde2}
description             x64_ADS2_Test_PE4-Gh11.5.1_2014-03-24
osdevice                ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh11.5.1_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {fd14773a-e55c-47e2-82d5-a4d9d23d3c52}
device                  ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.4570_2014-03-24.wim,{fb87959c-ff53-4415-8ea4-ce4843bdd1dc}
description             x64_ADS2_Test_PE4-Gh12.0.0.4570_2014-03-24
osdevice                ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.4570_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {e8bb16a3-4dfe-4ae2-9f97-7c4bb87dcc67}
device                  ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24.wim,{817e4a23-df42-4abb-9f8e-0ad2f00ce75c}
description             x64_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24
osdevice                ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.5505_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {a5e90e93-5616-4b03-b2a7-d5432d57d6f0}
device                  ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.5560_2014-03-24.wim,{16467a12-6ed1-4475-aaf5-2524ad038b7e}
description             x64_ADS2_Test_PE4-Gh12.0.0.5560_2014-03-24
osdevice                ramdisk=[boot]\Boot\x64\Images\x64_ADS2_Test_PE4-Gh12.0.0.5560_2014-03-24.wim,{68d9e51c-a129-4ee1-9725-2ab00a957daf}
systemroot              \WINDOWS
detecthal               Yes
winpe                   Yes

Hi,

How can I identify the no of Disk IO assigned to  Windows Server 2012 R2 machine`s Disk ??

Where i can see the Nos of I/O as 1200,2000 I/O etc.. through OS.

Shailendra Dev

Similar screenshot

sandip

I have a TechNet subscription and am supposed to get "priority support" but I mistakenly asked my question in one of the forums that is not in the "priority support monitored" list. Included here by reference:

http://social.technet.microsoft.com/Forums/windowsserver/en-US/bbbb34f2-e098-4f7d-b692-88e033869385/windows-server-2012r2-inplace-upgrade-from-2012-quotjust-quitsquot?forum=winserver2012r2previewsetup

Short description: On the 2012 DataCenter machine which serves as my Hyper-V host, I mount the install media and launch Setup. It starts, copies the temporary files ($windows.~bt) and then just quits.

Content of c:\windows\setupact.log:

2013-10-11 10:29:04, Info                  UI     Determining whether we should run ConX or legacy setup
2013-10-11 10:29:04, Info                  UI     Downlevel OS is server. Continue to run legacy setup
2013-10-11 10:29:04, Info                  UI     Determining if we are in WDS/Unattend mode
2013-10-11 10:29:04, Info                  UI     No need to hide autorun
2013-10-11 10:29:04, Info       [0x0a000a] UI     Autorun:Autorun core successfully  initialized!!!
2013-10-11 10:29:04, Info       [0x0a000b] UI     Autorun:Autorun UI successfully  initialized!!!
2013-10-11 10:29:04, Info                  UI     AppWindow has layout style 0
2013-10-11 10:29:04, Info                  UI     NavWindow has layout style 0
2013-10-11 10:29:04, Warning    [0x0a0180] UI     Failed to change the UI language to en-US.
2013-10-11 10:29:04, Info       [0x0a011c] UI     WizardDialogPost::SetActive
2013-10-11 10:29:09, Info       [0x0a018e] UI     Passing command line parameter ("H:\Sources\setup.exe /HideWelcome /uilanguage:en-US /targetlanguage:en-US") to IBS.

Would appreciate any suggestions that don't involve doing a detailed documentation capture of how the server is configured followed by a clean install, that is what I'm trying to avoid if possible.

I am not trying to do anything special or scripted, just a standard OS upgrade.

I am looking to migrate a KMS server from one 2012 R2 server to another. Reason is we're getting rid of the server KMS is on now since we no longer need that server taking up so much space. 

Am I correct in that this is the right approach? If not, please advise any recommended corrections:

Steps on "old" KMS server that will be decommissioned:

1. Gather the partial product keys that are installed, and find complete keys online, note the full keys
2. Disable DNS publishing by running "slmgr /cdns"
3. Uninstall KMS keys by running "slmgr /upk"
4. Clear keys from registry by running "slmgr /cpky"
5. shutdown the VM of server and wait until approved for deleting 

Steps on "new" KMS server":

1. Run "slmgr /upk"
2. Install KMS key for 2012 R2 Standard/Data edition (from the Volume licensing website for our organization) by running ?slmgr /ipk <the kms key from volume licensing website>. 
3. Activate with slmgr /ato
4. Disable DNS publishing
5. Update existing _VLMCS DNS record manually to point from old KMS server to the new KMS server hostname. 
6. Restart Software Protection Service with command "net stop sppsvc && net start sppsvc"
7. Download and install both the Office 2010 and Office 2013 Volume License Packs and install and add their KMS keys from our Volume Licensing website? 

Hi All,

I run discover product and update license status by VAMT successfuly, So I can find list of product with license status. But, I cannot find the list on Voleme Licensing Report "This report currently has no record", and I see the value on VAMT Inventory and License Overview is not upto date. How to solve this problem.

For detail, please find on my image.

List Product

No record on VAMT report

License Overview

Thanks,

Nana Sutisna

HI,

in need of some advise here.

i have done 2008R2 upgrade from STD to ENT using the bootup DVD method.(later on i  found out the DSIM method).

after upgrading, the system show 63.7GB RAM usable only but i have 112GB of actual RAM installed.

since 2008R2 ENT supports up to 2TB RAM, i guess the problem is caused after my upgrade.(shoud have use the public KMS key method).

anyway, im doing windows update now as i cant seems to find a solution right now on the internet. im also looking at reinstalled clean windows on my IBM server.

Btw, i have log a case with IBM and they have that it is not hardware DIMM error.

on my computer/system, i can see 112GB RAM (63.7 RAM usable)

pls let me know if anyone has a solution, appreciates...

ROnald

Hi All,

I am working on upgrading my domain to 2008. I currently have 2 2003 domain controllers, and will adding adding a new 2008 R2 domain controller to my domain and taking one of my 2003 domain controllers offline. 

I have ran all the Preps for this upgrade and am seeing a few errors in the dcpromo that I need help with. After I run the drpromo I am getting the following errors. Is it ok to continue without having an rodc on the domain?

I tried to install windows server 2008 r2 on my partition. When I select the partion, i got the error message "Windows can not be installed on this disk. The selected disk is of the GPT partition style"

Can anyone assist?

ss

I am unable to install Windows Mobile Device Center 6.1 on Windows 8 Release Preview, it is trying to download the latest files and not installing (just disappearing the windows), tried several times same problem, Even I tried with the compatibility option also.

Can any one suggest me a solution for syncing tool between my windows phone 6.X and my pc...

regards
Vinay

Regards Vinay

Hi I've searched the topics, but can't seem to find an answer to my particular problem.
I am trying to set up a WDS server to deploy Windows 7 on our network.
I started from scratch, installing Windows server 2008 R2 (Datacenter), I installed the WDS role (including Deployment and Transport Server).   Once installed, added a boot image. We have AD and DHCP on another server on the network. But when I try to PXE boot from a client PC, I get a 'No boot filename received' error.

Are there any other prerequisites needed? In all the the guides I've looked at, they don't say anything else is needed, but none seem to mention anything about PXE itself, is that all installed when WDS is added?

Thanks

Graham

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.

I can't  seem to get pxe working on my SCCM 2012

I followed the procedure of adding the DP and switching on PXE and letting is sort out WDS but I am getting a lot of error message in the distmgr.log and SMSPXE.log

I have attached the logs

Distmgr.log  - https://mega.co.nz/#!s8dxGZZA!Fq4j6YyLd8mjRu1Dec00bYD8Amo8DIAwrfwovRcTgDc

SMSPXE.log   - https://mega.co.nz/#!xpdmTAYS!VilJu-a6YmyF-7iFHGywQy4D4m2Dfu28q-_XUoRYsYY

I have tried everything from removing the DP role from the server removing the bootimages and rebooting and just seem to be going round in circle have spent nearly 2 days on this now/