Flagging Helpdesk VIPs Based on AD Groups
Let me start by saying I'm very new to Altiris and there may be a better solution than this.... And this is my first Juice post.
Here's a handy script we use to flag certain employees as VIPs in our Altiris Helpdesk system. Check it out.
Our company uses an automated process (Active Groups) which populates a group called, for example Executives. This group includes the Execs and their Administrative Associates and is updated on a daily basis. We wanted a way to automatically make members of this group VIPs in the Altiris Helpdesk and didn't see a way of doing it via the AD Connector (it might be possible - read first sentence.)
Instead I used the following script to look at our AD group and flag all of its members as VIPs. I simply run the script each night via scheduled tasks. Of course, you'll need to make some edits to get it to fit in your environment, but its pretty straightforward.

Very Good Script
Is required action into Active Directory Component Option.
This function need from Import Automatic AD with synchronization to Help Desk.
IT Consultant
Altiris Certified Engineer
Nice Script
This is great. Tried out on my test server with no issues. Definitely looks like something that should be made into an official product request for Helpdesk going forward.
John Golembiewski
Midwest Practice Principal
ITS Partners
Jgo@itsdelivers
other uses
With some modification, you could do queue membership updates with this. Just went through and it works pretty nice. Make the normal modifications and change the worker.queue_id = XX to whatever the id of the queue you want to work with is. You could probably expand this into a larger script that will update your queue memberships based on AD groups. No more manually updating that information!
Const SQLServer = "servername" 'edit this with the SQL server name
'connect to DB
Set oConn = CreateObject("ADODB.Connection")
oConn.Open "Driver={SQL Server};" & _
"Server=" & SQLServer & ";" & _
"Database=Altiris_Incidents;" & _
"Trusted_Connection=yes;"
'Get group membership - user the DN to connect to the object
Set objGroup = GetObject _
("LDAP://CN=TargetGroup,OU=SomeOU,DC=mydomain,DC=com") 'edit this with the DN of the group
'Loop through all group members
For Each Member In objGroup.getex("member")
Set objUser=GetObject ("LDAP://" & Member)
'altiris appends the domain in front of the nt user id - so we do the same here
strUserid = "mydomain\" & objUser.get("samaccountname") 'edit mydomain with the domain name
sSQL = "update worker set worker.queue_id = XX where worker.contact_id = (select contact.id from contact, worker where contact.id = worker.contact_id and contact.nt_id ='" & strUserid & "')"
Err.Clear
oConn.Execute(sSQL)
Set objUserid = Nothing
next
Set ObjGroup = Nothing
oconn.Close
Set oconn = Nothing
Works Great
We have been using this for sometime. It works great.
www.thesystemsengineer.com
Would you like to reply?
Login or Register to post your comment.