PSD icon indicating copy to clipboard operation
PSD copied to clipboard

could not connect to deplomentshare version 2.30

Open Audigy35 opened this issue 1 year ago • 12 comments

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.

Audigy35 avatar Sep 12 '24 09:09 Audigy35

Any logs you can share with us?

GeoSimos avatar Sep 12 '24 16:09 GeoSimos

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

Audigy35 avatar Sep 15 '24 06:09 Audigy35

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.

PowerShellCrack avatar Sep 16 '24 00:09 PowerShellCrack

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

How did you solve that problem?

Tokkiedekip avatar Sep 17 '24 08:09 Tokkiedekip

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

dubyatp avatar Sep 19 '24 15:09 dubyatp

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

PowerShellCrack avatar Sep 20 '24 19:09 PowerShellCrack

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

bretthexum avatar Sep 26 '24 16:09 bretthexum

So are we good to close this?

PowerShellCrack avatar Oct 02 '24 02:10 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

PowerShellCrack avatar Dec 29 '24 14:12 PowerShellCrack

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:

Image

SirBlizZ avatar Jan 20 '25 09:01 SirBlizZ

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.

PowerShellCrack avatar Jan 21 '25 17:01 PowerShellCrack

@GeoSimos can you close this one.

PowerShellCrack avatar Mar 22 '25 12:03 PowerShellCrack