-
Notifications
You must be signed in to change notification settings - Fork 15
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
WinRM error after using the xPendingReboot resource #48
Comments
Hi @yohanb, I haven't seen that one before. Looks like there are a few other bugs related to this in upstream packages:
Might be related? I suppose it's possible that WinRM just doesn't like the restart? |
I have not seen this error, but some similar. I think the join domain, set the required reboot in dsc itself and you need no xPendingReboot. But you need to configure your machine to do a reboot (I solved this currently with something like: https://github.com/mefellows/vagrant-dsc/blob/master/development/reboot/Vagrantfile#L4) What happens if you run after the reboot has finished a Can your share your vagrant and dsc file? |
@StefanSchoof sure! I've obviously removed any account info from the files. Vagrant file:
DSC LCM Config:
DSC file:
|
I will look at it, but this may take some time. |
I tried to reproduce and I do not get the error. I run Win10, Vagrant 1.9.1, Virtualbox 5.1.12. |
Thanks @StefanSchoof |
Hi,
I'm joining a domain using DSC after I have to reboot the machine afterwards. I'm using the xPendingReboot resource from the XComputerManagement module. I'm getting this error from Vagrant after DSC reboots the machine:
![image](https://cloud.githubusercontent.com/assets/812993/21404312/967af2ea-c78e-11e6-9ac4-6789ab70d056.png)
Any ideas? Thanks.
The text was updated successfully, but these errors were encountered: