An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.
One of a set of tools we're offering as a way of saying thank you for being a part of the community.
Solved
SCCM OSD HTA File
Posted on 2016-08-26
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
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
[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
Active today
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
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
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
The following article discusses and demonstrates the advantages of using Pull Distribution Points in SCCM 2012 SP1 or higher as opposed to traditional push based architecture
Binary Differential Replication, What it is, how it works and how it differs from standard delta file replication
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB.
How Percona can help
Percona can help you determine if Percona Server for MongoDB is the right solution for …
In this video, Percona Solution Engineer Rick Golba discuss how (and why) you implement high availability in a database environment.
To discuss how Percona Consulting can help with your design and architecture needs for your database and infrastr…
Suggested Courses
Course of the Month7 days, 17 hours left to enroll
715 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.