GordonPrice67
IS-IT--Management
I have a piece of software (Autodesk Revit) that requires a user install component, where the individual user must be logged in the do the initial launch of the software, and then customize the data that is seeded. Commonly a firm may be installing the software on tens to hundreds of machines, so automating the user side of the install is a huge time saver.
The approach I am looking at is to leverage Roaming Profiles, AutoAdminLogon & RunOnce reg keys to log in to the machine as each user, launch the software and modify the user data, then log out and log in as the next user. I plan to use the DeleteRoamingCache reg key to keep the local machine from getting swamped in roaming profiles.
The VBScript piece I am struggling with is automating the constantly changing username for the auto login. My thought is to have a comma delimited txt file with username, password pairs, and as each user finishes, it looks at the list, finds it's own name, then seeds AutoAdminLogon with the name and password that comes next. I am just wondering if this is the most elegant approach?
The plan is to do this on a VM where all users have rights to change AutoAdminLogon, and the VM will have nothing installed but Windows and Revit, so there SHOULDN'T be any extraneous stuff getting into the roaming profiles.
Thanks for any insights!
Gordon
The approach I am looking at is to leverage Roaming Profiles, AutoAdminLogon & RunOnce reg keys to log in to the machine as each user, launch the software and modify the user data, then log out and log in as the next user. I plan to use the DeleteRoamingCache reg key to keep the local machine from getting swamped in roaming profiles.
The VBScript piece I am struggling with is automating the constantly changing username for the auto login. My thought is to have a comma delimited txt file with username, password pairs, and as each user finishes, it looks at the list, finds it's own name, then seeds AutoAdminLogon with the name and password that comes next. I am just wondering if this is the most elegant approach?
The plan is to do this on a VM where all users have rights to change AutoAdminLogon, and the VM will have nothing installed but Windows and Revit, so there SHOULDN'T be any extraneous stuff getting into the roaming profiles.
Thanks for any insights!
Gordon