search

OSDeploy / OSD

OSD Shared Functions
MIT License
130 stars 54 forks source link

Add-WindowsPackage failed Issue #123

Closed trongtinh1212 closed 3 months ago

trongtinh1212 commented 3 months ago

Describe the bug Hi, I can create New-OSDCloudTemplate without no problem with Windows Server 2022 Lab - ADK and PE Sep 2023 version, but i tried in my production server 2019 - ADK and PE Sep 2023 have this issue,

gwblok commented 3 months ago

OSDCloud is not tested on Server OS.
If you're able to find a root cause (my guess is that it's using the DISM built into Server 2019, instead of the DISM in the ADK), and then provide code to resolve the issue, I'll try to test and add into the project.

trongtinh1212 commented 3 months ago

OSDCloud is not tested on Server OS. If you're able to find a root cause (my guess is that it's using the DISM built into Server 2019, instead of the DISM in the ADK), and then provide code to resolve the issue, I'll try to test and add into the project.

hi @gwblok sorry I don't have any clue for this issue, cuz my lab (no domain and using workgroup) work just fine but my prod server in my company faced this issue (have a domain). Using MDT to create bootimage just fine so i guess OSDCloud is using DISM built-in and not using from ADK

gwblok commented 3 months ago

@trongtinh1212, perhaps update your 2019 server to something newer. :-)

I'd recommend using your Windows 10 or 11 workstation to build your OSDCloud Template & WorkSpace, then you can copy the ISO or boot.wim to a server.

gwblok commented 3 months ago

I asked on Discord, someone else with a 2019 server was able to do it. My guess is there is something environmental related on your setup. I would recommend using a Windows 11 workstation to create your OSDCloud Templates / Workspaces