Quantcast
Channel: Setup Deployment forum
Viewing all articles
Browse latest Browse all 2818

Bug report: WDS Server, Browse button do not work in WDS installed in stand Alone mode!

$
0
0
                             
          
  • Browse button do not work in "Windows Deployment Services" console.

    This BUG exist also in  Windows Server 2012 R2.
    The BUG exist in English-US, French, and probably other languages (not related to a language)

    To produce the bug do the following:

    On www.msdn.com download Windows Server Technical Preview 

    At command prompt install WDS Server role in StandAlone mode with the folowing command:
    PowerShell  Add-WindowsFeature  WDS   -IncludeManagementTools   -IncludeAllSubfeature

    Initialize the WDS role "IN STAND ALONE MODE" with the folowing command:
    wdsutil /verbose  /progress  /initialize-server  /server:localhost /REMINST:C:\RemoteInstall   /StandAlone

    The bug exist only if WDS is installed in standalone mode !

    To create a "prestaged device" and associate to this device an answer file we need an "answer file".
    To reproduce the BUG  a simple text file can be created with notepad in C:\RemoteInstall\WDSClientUnattend folder with the name PC1.xml. The content of this file is not important to reproduce the BUG.

    Now we will create a local "Prestaged Device" and will try to associate with the already existent answer file that we have created C:\RemoteInstall\WDSClientUnattend\PC1.xml:

    ServerManager, Clic "Tools", select "Windows Deployment Services"

    Click "Servers", Click on the name of your server, Right Click "Prestaged Devices", Select "Add Device",

    ( Do not confuse "Prestages Devices" with "Active Directory Prestaged Devices" because "Active Directory Prestages devices is not available in Stand Alone mode),

    Name: PC1
    DeviceID: 123456123456, Clic "Next"

    On the page "Boot", Clic "Next"

    On the page "Client Unattend", to see the bug click "Browse", Clic "C:", Clic "RemoteInstall", Click "WDSClientUnattend", Clic "PC1.xml"

    You can see that the PC1.xml are NOT added as "Unattend File".

    BROWSE BUTTON FAIL TO ADD THE SELECTED ANSWER FILE ! You can clic Next buton but your selected file ARE NOT ASSOCIATED WITH THE PRESTAGED DEVICE.

    My opinion is: The path to Unattend file must be relative to C:\RemoteInstall and must NOT contain C:\Remoteinstall.

    If you clic on Browse button you will indicate a FULL PATH and this is not accepted because the BUG. Also if you fill manually a FULL PATH next to Unattend File this is not accepted. Only file path relative to C:\Remoteinstall are accepted. This can be very confusing for somebody who do not know this.

    WorkAround:
    Insted of clic on Browse button, you can write the relative path:  "WDSClientUnattend\PC1.xml",
    Clic Next, Click Back, You can see that Unattend File is WDSClientUnattend\PC1.xml and this is right.

    Conclusion: relative path are OK, Full path including C:\RemoteInstall are not accepted. Browse button do not work !


Viewing all articles
Browse latest Browse all 2818

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>