[Fencer128]

Hi,

I'm busy trying to tweak our RIS setup here at work. We get 3 different classes of user logging onto the server and I'd like to have 3 seperate image folders containing builds specific to each group of users on my RIS server. RIS has a server-side action that can be used to enumerate folders. Usually this is used in oschoice.osc and has the form:

<META SERVER ACTION="ENUM IMAGES">

Allegedly, according to MS (see http://www.microsoft.com/resources/documen...ed_dpl_KEMO.asp) you can change the directory enumerated to be a subdirectory of the usual "Images" folder.

However, I can't get this working. It looks like I'm not the only one (see http://groups.google.co.uk/group/microsoft...74a3afceec6023e). All I get for trying is a "The data is invalid" error in the RIS menu. I've tried placing the folder to be enumerated alongside "Images" as well as beneath it. I've tried concatenating the folder name and using the following syntax, but still to no avail:

<META SERVER ACTION="ENUM FOLDER">
<META SERVER ACTION="ENUM IMAGES FOLDER">

I have a workaround if this doesn't work out of using the "Images" directory and setting folder permissions for individual builds to give read access to only the appropriate group, but I'd rather do it the way above if possible. Anyone got this working?

Cheers ,

Andy

This post has been edited by Fencer128: 11 December 2005 - 11:52 AM

[RogueSpear]

I'm curious as to why you would want three different images. What I have always done is deploy the same image, it's a one size fits all, and then deploy software on a per OU basis. I also make extensive use of machine scripts (per OU) and user scripts (both per OU and based on security group membership) to further customize things.

Just to make sure I'm not misunderstanding things as well, are you attempting to use three flat images as opposed to three Riprep images? I'm asking all of this not to criticize your methods, but rather it's something I haven't done and am wondering if it's something I should consider.

[Fencer128]

Hi,

Thanks for replying.

Firstly, the images are all flat - no riprpep. For the desktop stuff I use RVM and BTS packs - so they are "one size fits all". We use SMS for all our software deployment/auditing and so I'm not conerned with that aspect.

Secondly, having 3 different groups of images is only part of the reason I need different image folders. This RIS server is responsible for deploying 3 types of build:

1. Customised XP SP2 (Desktop clients ~2000 on campus)
2. Vanilla XP SP2 (used by our student lab staff to build master ghost images for multicasting ~800 lab machines that require quick and frequent rebuilds)
3. Server 2k3 SP1 (Used by our systems people for server room stuff ~50 machines as far as I know)

Ideally each group of people should only have access to their own builds and no-one elses (i.e. no reading/editing/etc). This is the first reason for creating 3 seperate folders. I realise there are other ways to achieve this security by setting permissions on each individual build folder, or by using GPO and META SERVER ACTION but I'd rather do it this way if possible.

The second reason is that the way in which people in each group want to use RIS is different. This necessitates 3 seperate osc file paths through to build selection and finally deployment. These are:

1. Choice of OU from particular part of AD schema, no auto install option, display data input screen (Desktop clients)
2. Automatic OU choice from different domain, auto skip to warning screen with single key press. (Student lab)
3. Choice of OU from different part of AD schema again, no display data input (Server stuff).

So you can see that I have 3 different paths to accomodate 3 different usages of RIS. There are also seperate builds available to each path/group.

Hope that's clear!

Andy

This post has been edited by Fencer128: 09 December 2005 - 09:21 AM

[RogueSpear]

Ok, well now that I have a context I can start to look into this. Also, as I had thought, you gave me some ideas that I could use as well I'll let you know what I come up with..

[Fencer128]

Good luck, especially if you are going to try enumerating folders other than "Images" for sif files

Andy

[RogueSpear]

Well actually what I was going to give a shot, prolly not today though, is using NTFS permissions. Also I seem to remember some permission options here and there in the DSA snapin.

[Fencer128]

Hi,

You can select what builds/images users see in the oschoice.osc screen by setting the NTFS read permissions on each images sif file. Denying a user read permission effectively hides it from them so it is not enumerated.

This will allow you to stop certain users/groups from being able to access certain images through thr RIS menu system.

Cheers,

Andy

[Fencer128]

Hi,

I've found a mistake in a custom osc file that I think is the root cause of this problem... Basically I'm giving contradictory information as to what screen to move onto once a selection has been made. Two instructions come from having the following on the same page:

<META KEY=ENTER HREF="OSCHOICE">
.
.
.
<OPTION VALUE="D_OSCHOICEX8632">

I'll correct this on Monday and post the result.

Andy

This post has been edited by Fencer128: 11 December 2005 - 01:37 PM

[Fencer128]

Hi,

I was right in that removing:

<OPTION VALUE="D_OSCHOICEX8632">

fixed a problem (but it was not the complete solution).

Now RIS was enumerating the correct folder, but telling me there were no OS contained within. I tracked this problem back to incorrect MS documentation. The guide says:

Quote

Enumerates the Setup Information File (SIF) under the X:\RemoteInstall\Setup %LANGUAGE%\images\ "directory" name.

but it should read:

Quote

Enumerates the Setup Information File (SIF) under the X:\RemoteInstall\Setup %LANGUAGE%"directory" name.

If you place your custom folder containing the OS to be enumerated at the same level as "Images", then the SIF files are enumerated.

Hope that is clear!

Andy

This post has been edited by Fencer128: 12 December 2005 - 05:05 AM