We currently deployed WS1 successfully using Airlift & SCCM to 80% if our company with no issues. However, we have around 150 Windows 10 devices we need to enroll with the same user (an admin user) s...
See more...
We currently deployed WS1 successfully using Airlift & SCCM to 80% if our company with no issues. However, we have around 150 Windows 10 devices we need to enroll with the same user (an admin user) silently due to production workflow. Through all my reading and testing, I have not found a reliable way to do this. Wanted to reach out to the community to see if anyone has done this or has a solution, before contacting support. Notes on troubleshooting and testing: - The machines must be enrolled to a specific Org group due to applied profiles - The machines have multiple users on a daily basis and no owner - these users are not in WSOne nor should they be. - They live in an extremely large warehouse that is 24/6 production, with power shut down the 7th day. - They are prod machines so there is next to 0 available time to access them to enroll manually. Default cmd using staging user: msiexec.exe /i AirWatchAgent.msi /qn ENROLL=Y IMAGE=N SERVER=<server> LGNAME="WHdesktops" USERNAME="wsoneadmin" PASSWORD="<password>" EOBO test: msiexec.exe /i AirWatchAgent.msi /qn ENROLL=Y IMAGE=N SERVER=<server> LGNAME="WHdesktops" USERNAME="wsoneadmin" PASSWORD="<password>" STAGEUSERNAME="wsoneadmin" STAGEPASSWORD="<password>" /log %TEMP%\AWAgent.log - User is configured as a staging user - All certificates are current and working - When using "Default cmd" the device enrolls, but the user is a staging user and still pops up asking for username/pw. - I have read all the VMWare KB information available on techzone and WorkspaceONE regarding this with no definite answer.