Solved

SCCM OSD HTA File

Posted on 2016-08-26
2
57 Views
Last Modified: 2016-09-20
Hi All,

The interface needs to capture the following information:
•      User of the Device and/or location.  This will go in the AD “Description” field.
•      Employee’s ID.  This will need to go into the AD “EmployeeID” field in attribute.
•      The OU to put the device in correct OU.

All of that information needs to be written to AD during the image process, likely after the device joins the domain so we don’t have permissions issues.  That’ll mean storing as Task Sequence variables. the AD OU portion to be forced choice, meaning the tech’s will have a list to choose from (e.g. dropdown/combo box).

Can anyone please provide a script or HTA file
0
Comment
Question by:Gaurav Singh
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
2 Comments
 
LVL 18

Accepted Solution

by:
Mike T earned 500 total points (awarded by participants)
ID: 41772913
Hi,

That's a very ask, especially for free! I once re-wrote a HTA that joined the domain and validated the name, but nothing as complex as what you are asking.

The fundamental problem with each piece of info is that you are asking a human to type into a free form field, and with the best will in the world, people make mistakes and mis-type data or worse, get lazy and type any old rubbish just to get rid of the form. Most of the effort I spent on the HTA was to use a regular expression to heavily restrict what anyone could enter.

Do you have any such restrictions? Not allowing symbols (only alpha-numeric) is probably top of the list.

With regards the AD user, location and Employee ID, this requires an account setup with write permissions to AD. How do you use the info later? I'm just wondering how necessary it is. I've found that managers ask for X and it's done and no-one ever, ever makes use of the info.
It also predicates that machines belong to specific users and never move. Is that really true?

As for the Move OU step, that's the easiest, with a VBS script and a parameter, but how many OUs do you have to move to? I generally worked on systems that kept it simple: one OU that was either desktop or laptop. This meant machine types were treated equally, so it didn't matter what role users do.

You need to give a bit more detail, as above.

Mike
0
 
LVL 18

Expert Comment

by:Mike T
ID: 41806187
This question is really more suited to a consultancy piece of work - i.e. not free; I can give advice but don't have time or resources to give a full solution and neither do other experts.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
SCCM Reporting 5 87
Unlicencing Windows 7 x86 via VAMT? 3 92
Software installation of SCCM client 14 232
Unable to create driver package in SCCM 6 40
The following article is intended as a guide to using PowerShell as a more versatile and reliable form of application detection in SCCM.
An article on effective troubleshooting
I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below. https://filedb.experts-exchange.com/incoming/2017/03_w12/1151775/Permutations.txt https://filedb.experts-exchange.com/incoming/201…
Suggested Courses

751 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question