could not connect to deplomentshare version 2.30

[Audigy35]

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]

Any logs you can share with us?

[Audigy35]

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

[PowerShellCrack]

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]

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

How did you solve that problem?

[dubyatp]

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]

You have a good point. It should be documented. I have developed documentation for it and submitted a pull request #183

[bretthexum]

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]

So are we good to close this?

[PowerShellCrack]

Can you check your configurations against this: https://github.com/FriendsOfMDT/PSD/blob/CurrentDev/Documentation/PowerShell%20Deployment%20-%20Latest%20Release%20Setup%20Guide.md#review-psd-install

This should solve the issues

[SirBlizZ]

Hey it took me a while to figure it out with the bootstrap.ini file, with this post.
-> The new updated documentation is good to understand
-> The post from dubyatp is the solution
-> After changing the bootstrap.ini, update the deployment share

Here is a screenshot for completion, from my lab:

[PowerShellCrack]

That is good to hear. Yes, having the PSD properties populated in the new version will break it. I'm hoping the changed and new documentations I made will be pulled into the main repo.