Friday, January 09, 2009
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Member Login
StandardLiveID


Register
Forgot Password ?



Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Subject: Laptop / workstation location OUs
Prev Next
You are not authorized to post a reply.

AuthorMessages
NickspUser is Offline

Posts:3

Send Message
08/06/2008 11:06 PM  

Hi all,

I have set up a basic WDS lite touch deployment system using a deployment DB.

Based on the location, the client OU is specified.

EG Location SYD - ou=Sydney,ou=systems

Location BNE - ou=Brisbane,ou=systems

All good, however, the requirements are now changed... There are now seperate OUs created under each location OU for Laptops and Desktops.

 This means that we need to determine location AND machine type to specify the OU.

We would prefer to keep all of the configuration within the DB, but can edit cs.ini if needed.

 

Any thoughts on how best to get this working?

 

 

 

 

 
bn2huntUser is Offline

Posts:95

Send Message
08/07/2008 7:53 AM  

My first thought would be to use the Cs.ini and a userexit script to set the OU.  I think something like this would work

[code]

customsettings.ini

priority = OUalias,...

[OUalias]
oualias = #setOUalias#
userexit = userexit.vbs

[mmsettings]
...
MachineObjectOU=oualias

userexit.vbs

 

Function UserExit(sType, sWhen, sDetail, bSkip)
 oLogging.CreateEntry "entered UserExit ", LogTypeInfo
 UserExit = Success
End Function

Function setoualias ()
 oLogging.CreateEntry "Entered UserExit Function setoualias" , LogTypeInfo
 On Error Resume Next
 
 select case location
  case "SYD"
   setoualias = "ou=Sydney"
  case "BNE"
   setoualias = "ou=Bisbane"
 end select
 if islaptop then setoualias = setoualias & ",ou=laptop"
 if isdesktop then setoualias = setoualias & ",ou=deskop"
 if isserver then setoualias = setoualias & ",ou=server"
end function

[/code]

 

Not sure if that would work but that is where I think I would start.  You might even be able to use the function name in the database as a variable, but I'm not sure.

 

Good luck

NickspUser is Offline

Posts:3

Send Message
08/07/2008 5:55 PM  
Thanks for that - I will give it a go and let you know how it goes

Nick
NickspUser is Offline

Posts:3

Send Message
08/18/2008 5:21 AM  

I have nearly got this working... but I am having an issue with the location variable/property.

I have setup a UserExit in cs.ini like this...

 .From memory...at home...

 [Settings]

 Priorities=CSettings, Locations, OULookup,...

 [OULookup]

MachineObjectOU=OULookup(%LOCATION%,%IsLaptop%,%IsDesktop%,%IsServer%)

UserExit=UserExit.VBS

 In UserExit.vbs the function is

 Function OULookup(sLoc,bLaptop,bDesktop,bServer)

'Read variables and do stuff

End Function

 All of the IsMachine True/False variables pass through to the function, but not the location data. I have also tried to reference a vbs global variable 'location' in the script - no success.

The Location data is set by the higher priority section in cs.ini when it queries the DB with its subnet. BDD.log shows this section gets a property:value called Location001:SYD and this is copied to the Location property.

OULookup function happens immediatley after the first Location DB lookup, before all the roles, settings, etc are queried.

 I am a bit stumpted!

 Should I be referencing Location in a different way? Am I able to use a 'DB generated' Location variable in a userexit script?

Any suggestions?

 

Nick

 

 
You are not authorized to post a reply.
Forums > Deployment Solutions > MDT 2008 > Laptop / workstation location OUs



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.



Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt