-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Browse failures on 1709 DataCenter server #75
Comments
Hi John! Sure, ill add there a way to specify media in labconfig. I prefer using 1709 win 10, it's way easier. There are also ways how to extract failover clustering from server, so you can have shared vhd in there. |
Would you more like a prompt where you would type location? Or folders where you would just copy ISO/msu files? Or just ability to specify paths in labconfig? |
And btw does it make sense to use 1709 as host? You connect to it remotely? Im wondering if I should rewrite it to be able to deploy lab to remote server... |
I’d personally be happy enough with a “Please enter the full file path to the <client / server> ISO – ie. D:\ISOs\Win1709.iso” – the problem I see with just a folder path is the filename itself may not stay the same month to month, and people themselves may choose to rename it from the MS filename convention..
From: Jaromir Kaspar [mailto:notifications@github.com]
Sent: Sunday, 12 November 2017 11:49 PM
To: Microsoft/ws2016lab <ws2016lab@noreply.github.com>
Cc: Joshua Clarke <jclarke@fcit.com.au>; Author <author@noreply.github.com>
Subject: Re: [Microsoft/ws2016lab] Browse failures on 1709 DataCenter server (#75)
Would you more like a prompt where you would type location? Or folders where you would just copy ISO/msu files? Or just ability to specify paths in labconfig?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#75 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AbcdgItx60P3c1odeC4p5LDxLhDrSSBCks5s1ulTgaJpZM4Qa1QK>.
|
I was tossing up whether to install 1709 or stick with 2016 server on the host, but decided to go with 1709 as it has the network controller, updated GPU passthrough, etc. and if I needed S2D I could just virtualise that portion of it with a 2016 VM or two.
My use case is probably far from the norm, but I’m using a dedicated server at a public DC as my host, so I don’t have LAN access to join it to my domain directly. I did try to psremote to it to run your scripts (hoping I’d get the gui on the local client), but that didn’t quite work either.
Thanks!
Josh
From: Jaromir Kaspar [mailto:notifications@github.com]
Sent: Sunday, 12 November 2017 11:51 PM
To: Microsoft/ws2016lab <ws2016lab@noreply.github.com>
Cc: Joshua Clarke <jclarke@fcit.com.au>; Author <author@noreply.github.com>
Subject: Re: [Microsoft/ws2016lab] Browse failures on 1709 DataCenter server (#75)
And btw does it make sense to use 1709 as host? You connect to it remotely? Im wondering if I should rewrite it to be able to deploy lab to remote server...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#75 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AbcdgBlBpQFKWU6Z4H1Gly8RiiGxOl0tks5s1unGgaJpZM4Qa1QK>.
|
Cool. Can you try this? :) https://github.com/Microsoft/ws2016lab/raw/dev/scripts.zip |
Hi Jaromir,
Created a new folder on the host for the updated files, #1 ran through fine, #2 failed at the start of script looking for the ISO. Here’s the output:
Couldn’t find the transcript files to attach either, has that changed ?
[cid:image001.png@01D35FD5.E1B5B0D0]
PS C:\Scripts\ws2016lab-dev-20171117> .\2_CreateParentDisks.ps1
Security warning
Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your
computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning
message. Do you want to run C:\Scripts\ws2016lab-dev-20171117\2_CreateParentDisks.ps1?
[D] Do not run [R] Run once [S] Suspend [?] Help (default is "D"): r
Transcript started, output file is C:\Scripts\ws2016lab-dev-20171117\CreateParentDisks.log
Script started at 11/17/2017 18:52:54
Checking if Hyper-V is installed
Hyper-V is Installed
Checking if Hyper-V Powershell module is installed
Hyper-V is Installed
Testing if some parent disk already exists and can be used
VHD eligible for DC not found. VHD for DC will be created after ParentDisks are created.
Win2016Core_G2.vhdx not found, will be created
Win2016NanoHV_G2.vhdx not found, will be created
Tools.vhdx not found, will be created
Please select ISO image with Windows Server 2016, 1709 or later
GAC Version Location
--- ------- --------
True v4.0.30319 C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089...
Exception calling "ShowDialog" with "0" argument(s): "Creating an instance of the COM component with CLSID
{DC1C5A9C-E88A-4DDE-A5A1-60F82A20AEF7} from the IClassFactory failed due to the following error: 80040111 ClassFactory
cannot supply requested class (Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE))."
At C:\Scripts\ws2016lab-dev-20171117\2_CreateParentDisks.ps1:326 char:20
+ If($openFile.ShowDialog() -eq "OK"){
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : COMException
Iso was not selected... Exitting
Press enter to continue ...
From: Jaromir Kaspar [mailto:notifications@github.com]
Sent: Monday, 13 November 2017 9:54 PM
To: Microsoft/ws2016lab <ws2016lab@noreply.github.com>
Cc: Joshua Clarke <jclarke@fcit.com.au>; Author <author@noreply.github.com>
Subject: Re: [Microsoft/ws2016lab] Browse failures on 1709 DataCenter server (#75)
Cool. Can you try this? :) https://github.com/Microsoft/ws2016lab/raw/dev/scripts.zip
See LabConfig for examples. You can specify folders for both ISO and MSUs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#75 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AbcdgIy1ALY23mDwQo4qaoXegGLHJp8Xks5s2B_FgaJpZM4Qa1QK>.
|
Sorry, hold that thought – will populate the new variables and try again..
From: Joshua Clarke
Sent: Friday, 17 November 2017 6:57 PM
To: 'Microsoft/ws2016lab' <reply@reply.github.com>; Microsoft/ws2016lab <ws2016lab@noreply.github.com>
Cc: Author <author@noreply.github.com>
Subject: RE: [Microsoft/ws2016lab] Browse failures on 1709 DataCenter server (#75)
Hi Jaromir,
Created a new folder on the host for the updated files, #1 ran through fine, #2 failed at the start of script looking for the ISO. Here’s the output:
Couldn’t find the transcript files to attach either, has that changed ?
[cid:image001.png@01D35FD6.31F0EFB0]
PS C:\Scripts\ws2016lab-dev-20171117> .\2_CreateParentDisks.ps1
Security warning
Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your
computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning
message. Do you want to run C:\Scripts\ws2016lab-dev-20171117\2_CreateParentDisks.ps1?
[D] Do not run [R] Run once [S] Suspend [?] Help (default is "D"): r
Transcript started, output file is C:\Scripts\ws2016lab-dev-20171117\CreateParentDisks.log
Script started at 11/17/2017 18:52:54
Checking if Hyper-V is installed
Hyper-V is Installed
Checking if Hyper-V Powershell module is installed
Hyper-V is Installed
Testing if some parent disk already exists and can be used
VHD eligible for DC not found. VHD for DC will be created after ParentDisks are created.
Win2016Core_G2.vhdx not found, will be created
Win2016NanoHV_G2.vhdx not found, will be created
Tools.vhdx not found, will be created
Please select ISO image with Windows Server 2016, 1709 or later
GAC Version Location
--- ------- --------
True v4.0.30319 C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089...
Exception calling "ShowDialog" with "0" argument(s): "Creating an instance of the COM component with CLSID
{DC1C5A9C-E88A-4DDE-A5A1-60F82A20AEF7} from the IClassFactory failed due to the following error: 80040111 ClassFactory
cannot supply requested class (Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE))."
At C:\Scripts\ws2016lab-dev-20171117\2_CreateParentDisks.ps1:326 char:20
+ If($openFile.ShowDialog() -eq "OK"){
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : COMException
Iso was not selected... Exitting
Press enter to continue ...
From: Jaromir Kaspar [mailto:notifications@github.com]
Sent: Monday, 13 November 2017 9:54 PM
To: Microsoft/ws2016lab <ws2016lab@noreply.github.com<mailto:ws2016lab@noreply.github.com>>
Cc: Joshua Clarke <jclarke@fcit.com.au<mailto:jclarke@fcit.com.au>>; Author <author@noreply.github.com<mailto:author@noreply.github.com>>
Subject: Re: [Microsoft/ws2016lab] Browse failures on 1709 DataCenter server (#75)
Cool. Can you try this? :) https://github.com/Microsoft/ws2016lab/raw/dev/scripts.zip
See LabConfig for examples. You can specify folders for both ISO and MSUs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#75 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AbcdgIy1ALY23mDwQo4qaoXegGLHJp8Xks5s2B_FgaJpZM4Qa1QK>.
|
That’s working a treat after populating the right fields ! I’m just running Step 3 now to be certain, but all looking good at this stage. Thanks for making those changes!
Update: Step 3 finished without a problem!
Three suggestions:
* In Step 2 - Do a try/catch for the error I got and advise the user that as he’s running on a non-GUI OS he’ll need to populate the Client/Server media variables, and MSU’s.
* LabConfig – For the average punter the shortened $LabConfig may confuse. Might be better to move the detailed one to the top of the script, and move the shortened one underneath. I’d also set the detailed one to active myself; maybe a personal preference though..
* Stop the transcript on fail?
Thanks again, I’m off to play with S2D now and probably spend the rest of the night trying to automate myself – you’ve inspired me!
Cheers,
Josh
From: Joshua Clarke
Sent: Friday, 17 November 2017 6:59 PM
To: 'Microsoft/ws2016lab' <reply@reply.github.com>; 'Microsoft/ws2016lab' <ws2016lab@noreply.github.com>
Cc: 'Author' <author@noreply.github.com>
Subject: RE: [Microsoft/ws2016lab] Browse failures on 1709 DataCenter server (#75)
Sorry, hold that thought – will populate the new variables and try again..
From: Joshua Clarke
Sent: Friday, 17 November 2017 6:57 PM
To: 'Microsoft/ws2016lab' <reply@reply.github.com>; Microsoft/ws2016lab <ws2016lab@noreply.github.com<mailto:ws2016lab@noreply.github.com>>
Cc: Author <author@noreply.github.com<mailto:author@noreply.github.com>>
Subject: RE: [Microsoft/ws2016lab] Browse failures on 1709 DataCenter server (#75)
Hi Jaromir,
Created a new folder on the host for the updated files, #1 ran through fine, #2 failed at the start of script looking for the ISO. Here’s the output:
Couldn’t find the transcript files to attach either, has that changed ?
[cid:image001.png@01D35FEB.099661C0]
PS C:\Scripts\ws2016lab-dev-20171117> .\2_CreateParentDisks.ps1
Security warning
Run only scripts that you trust. While scripts from the internet can be useful, this script can potentially harm your
computer. If you trust this script, use the Unblock-File cmdlet to allow the script to run without this warning
message. Do you want to run C:\Scripts\ws2016lab-dev-20171117\2_CreateParentDisks.ps1?
[D] Do not run [R] Run once [S] Suspend [?] Help (default is "D"): r
Transcript started, output file is C:\Scripts\ws2016lab-dev-20171117\CreateParentDisks.log
Script started at 11/17/2017 18:52:54
Checking if Hyper-V is installed
Hyper-V is Installed
Checking if Hyper-V Powershell module is installed
Hyper-V is Installed
Testing if some parent disk already exists and can be used
VHD eligible for DC not found. VHD for DC will be created after ParentDisks are created.
Win2016Core_G2.vhdx not found, will be created
Win2016NanoHV_G2.vhdx not found, will be created
Tools.vhdx not found, will be created
Please select ISO image with Windows Server 2016, 1709 or later
GAC Version Location
--- ------- --------
True v4.0.30319 C:\Windows\Microsoft.Net\assembly\GAC_MSIL\System.Windows.Forms\v4.0_4.0.0.0__b77a5c561934e089...
Exception calling "ShowDialog" with "0" argument(s): "Creating an instance of the COM component with CLSID
{DC1C5A9C-E88A-4DDE-A5A1-60F82A20AEF7} from the IClassFactory failed due to the following error: 80040111 ClassFactory
cannot supply requested class (Exception from HRESULT: 0x80040111 (CLASS_E_CLASSNOTAVAILABLE))."
At C:\Scripts\ws2016lab-dev-20171117\2_CreateParentDisks.ps1:326 char:20
+ If($openFile.ShowDialog() -eq "OK"){
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : COMException
Iso was not selected... Exitting
Press enter to continue ...
From: Jaromir Kaspar [mailto:notifications@github.com]
Sent: Monday, 13 November 2017 9:54 PM
To: Microsoft/ws2016lab <ws2016lab@noreply.github.com<mailto:ws2016lab@noreply.github.com>>
Cc: Joshua Clarke <jclarke@fcit.com.au<mailto:jclarke@fcit.com.au>>; Author <author@noreply.github.com<mailto:author@noreply.github.com>>
Subject: Re: [Microsoft/ws2016lab] Browse failures on 1709 DataCenter server (#75)
Cool. Can you try this? :) https://github.com/Microsoft/ws2016lab/raw/dev/scripts.zip
See LabConfig for examples. You can specify folders for both ISO and MSUs
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#75 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AbcdgIy1ALY23mDwQo4qaoXegGLHJp8Xks5s2B_FgaJpZM4Qa1QK>.
|
That's a great feedback. Let me add it tonight. |
Fixed in Dev branch. It should throw error, stop transcript and exit. Let me know if anything else. I'll close this issue then. |
Merged to master. Closing the issue. Thank you for heads up! |
Hi,
I tried to run these (faaantastic! Thankyou..) scripts on a 1709 release of Server 2016 DataCenter edition, and whenever it went prompting for ISO / MSU / etc media, the script would fail. Obviously there is no 'real' gui in 1709. The fix was to manually comment out the browse for server and client ISO media lines and manually pop in the file path at the mount-image step.
All ran fine after that. Hopefully there is a way to prompt for media on the console rather than selecting in explorer ?
Thanks, and great work!
Josh
The text was updated successfully, but these errors were encountered: