Support Multiple Shares

[LOldfield]

I was attempting today to get PSD setup across two deployment shares on the same host, with the aim of segregating endpoint and server deployments

I ran Install-PSD.ps1 per share, then New-PSDWebInstance.ps1 once to spin up IIS Running Set-PSDWebInstance.ps1 per share results in both appearing in IIS: And I've copied across the certificate, required rules and credentials, adjusted to point to "PSDServerProduction" The issue is that the new image seems to default to the existing "PSDProduction" virtual drive rather than the "PSDServerProduction", I only end up seeing the Task Sequences hosted in PSDProduction I suppose my question is what do I need to adjust to make this work - is it a property hardcoded into the image at build time? Or a property is IIS that's forcing my image back to the PSDProduction url?

[GeoSimos]

The WinPE boot image supports only one Deployment Share (DS), so what you have to do it setup each deployment share's "BootStrap.ini" file to point to your required share. Then you have to rebuild your WinPE boot images for each DS. Generally, when you change anything in BootStrap.ini, you must rebuild the boot image to reflect. Sample bootstrap.ini for your case:

[Settings]
Priority=PSDRoots,Default
Properties=PSDDebug, PSDDeployRoots,PSDPrestartMode

[PSDRoots]
PSDDeployRoots=https://mdt01.corp.viamonstra.com/psdproduction
;UserDomain=MDT01
;UserID=MDT_BA
;UserPassword=P@ssw0rd

[Default]
SkipBDDWelcome=YES
PSDPrestartMode=Native
PSDDebug=NO

and

[Settings]
Priority=PSDRoots,Default
Properties=PSDDebug, PSDDeployRoots,PSDPrestartMode

[PSDRoots]
PSDDeployRoots=https://mdt01.corp.viamonstra.com/psdserverproduction
;UserDomain=MDT01
;UserID=MDT_BA
;UserPassword=P@ssw0rd

[Default]
SkipBDDWelcome=YES
PSDPrestartMode=Native
PSDDebug=NO

If you use WDS, you can attach the boot images (the .wim files) and have them selected from a menu via PXE boot.