$oem$ folder in custom not working

Antworten
ritsovih
Beiträge: 38
Registriert: 20 Mär 2013, 09:25

$oem$ folder in custom not working

Beitrag von ritsovih »

Hi,

I've got a script that I want to run via SetupComplete.cmd as described here:

https://docs.microsoft.com/en-us/window ... dows-setup

I use a $OEM$ folder structure to deploy my SetupComplete.cmd script as described here:

https://docs.microsoft.com/en-us/previo ... 8(v=ws.10)

this setup works if I put the necessary file/folder structure under installfiles/sources/$OEM$ but according to https://download.uib.de/opsi4.0/doc/htm ... -structure

I think it should also work if I put it under custom/$oem$ but it doesn't

Works:

Code: Alles auswählen

installfiles/
│   ├── $OEM$
│   │   └── $$
│   │       ├── scripts
│   │       │   └── tpm.vbs
│   │       ├── Setup
│   │       │   └── scripts
│   │       │       ├── edit-libraries.cmd
│   │       │       └── SetupComplete.cmd
│   │       └── tools
│   │           └── SLUtil.exe
Does not work:

Code: Alles auswählen

custom/
│   ├── $oem$
│   │   └── $$
│   │       ├── scripts
│   │       │   └── tpm.vbs
│   │       ├── Setup
│   │       │   └── scripts
│   │       │       ├── edit-libraries.cmd
│   │       │       └── SetupComplete.cmd
│   │       └── tools
│   │           └── SLUtil.exe
is this a bug or am I doing it wrong?
andré
Beiträge: 324
Registriert: 07 Jan 2014, 10:48

Re: $oem$ folder in custom not working

Beitrag von andré »

The description behind custom/$oem$ says, that it works only under NT5. I guess you want to install Windows 10 or 7.
ritsovih
Beiträge: 38
Registriert: 20 Mär 2013, 09:25

Re: $oem$ folder in custom not working

Beitrag von ritsovih »

Thx, good call. Kinda strange that it only works for XP, since the general mechanics still work with Windows 10. But I was just curious. Doesn't really matter.
Antworten