search

FriendsOfMDT / PSD

PowerShell Deployment
MIT License
523 stars 81 forks source link

could not connect to deplomentshare version 2.30 #175

Open Audigy35 opened 1 month ago

Audigy35 commented 1 month ago

after ugrading to version 2.30 could not connect to deploymentshare i had to reinstall version 2.28 and i now can connect to the deploymentshare.

GeoSimos commented 1 month ago

Any logs you can share with us?

Audigy35 commented 1 month ago

i solved the connection the deploymentshare but now it always wants to run a tasksequence

PowerShellCrack commented 1 month ago

Sounds like you have a default Task sequence set with SkipTasksequence=YES or your hard drive has residual OSD process on it. Do a diskpart clean and restart PSD.

Tokkiedekip commented 1 month ago

i solved the connection the deploymentshare but now it always wants to run a tasksequence

How did you solve that problem?

dubyatp commented 1 month ago

I came across this as well after upgrading to 2.30, thought it was related to moving PSD from our testing environment to our production server (replacing our old MDT), but I reverted back to 2.29 and it worked as expected.

I did some digging in the diffs and noticed there were some changes to the default Bootstrap.ini file, particularly the removal of the PSDDebug, PSDDeployRoots,PSDPrestartMode line within Properties=

I removed PSDDebug, PSDDeployRoots,PSDPrestartMode from Properties= , upgraded back to 2.30, rebuilt the boot image, and it works as expected now :-)

This was definitely a breaking change that should be documented somewhere, or even better, perhaps provide a notice of the change when calling for an upgrade on Install-PSD.ps1 -- but other than that, it was an easy fix :D

PowerShellCrack commented 1 month ago

You have a good point. It should be documented. I have developed documentation for it and submitted a pull request https://github.com/FriendsOfMDT/PSD/pull/183

bretthexum commented 1 month ago

I came across this as well after upgrading to 2.30, thought it was related to moving PSD from our testing environment to our production server (replacing our old MDT), but I reverted back to 2.29 and it worked as expected.

I did some digging in the diffs and noticed there were some changes to the default Bootstrap.ini file, particularly the removal of the PSDDebug, PSDDeployRoots,PSDPrestartMode line within Properties=

I removed PSDDebug, PSDDeployRoots,PSDPrestartMode from Properties= , upgraded back to 2.30, rebuilt the boot image, and it works as expected now :-)

This was definitely a breaking change that should be documented somewhere, or even better, perhaps provide a notice of the change when calling for an upgrade on Install-PSD.ps1 -- but other than that, it was an easy fix :D

Same issue here. Had to comment out the bootstrap.ini differences and it worked

PowerShellCrack commented 1 month ago

So are we good to close this?