Do we really need to log in as new employees to prepare their laptops?

November 18, 2026 5 answers
Asked by _y47+torvexa.3

Our identity system enables new employee accounts before their start dates. Desktop support then uses the employee's credentials to create a Windows profile before shipping the laptop and asks for specific AD logon hours.

There's no documented policy for the restrictions, and an incorrect schedule has already blocked a new starter. Is there a technical reason for this setup, or is there a better way to handle it?

Answers

7c~brassotter_284

Using the employee's credentials is the bigger concern. Even if the password is temporary and gets reset, support is still acting as that user, which muddies accountability and creates another credential handoff.

Separate device preparation from user authentication. Use your existing management tools to image or provision the laptop, join it to the domain, and install what you can at the device level. Then let the employee create their own profile at first sign-in. Test the actual application setup before declaring the old step unnecessary.

_a76!kelvuno.4:

Some applications still have per-user setup at first sign-in. That may need scripting or a change in expectations rather than a technician signing in as the employee.

Reply to this answer
9j!sprocketfig_426

Check the remote first-login path before removing the step. If the laptop is going to someone who cannot reach a domain controller from the sign-in screen, a first domain sign-in may fail. A cached profile and credentials can be a workaround, but that does not make credential sharing a good default.

Test a freshly provisioned laptop on an external network and document how the new employee will authenticate. The right fix depends on your domain, VPN, and device management setup. The requested logon hours are a separate question, and there is nothing here showing why profile creation requires a particular schedule.

Reply to this answer
5x+quendaro_293

Run a small pilot instead of arguing over whether the old process is archaic. Take a test account and a freshly prepared device through first sign-in, then check the applications and settings support currently configures by hand. Note what works, what needs automation, and what the employee would have to finish.

That gives everyone something concrete to review. Big applications and user-specific configuration may take more work than a standard image, and a cloud management product is not necessarily available or affordable in every environment.

Reply to this answer
_b38+drivnelo.5

Ask for the written requirement and the reason behind the logon hours. If there isn't one, draft a short onboarding procedure with your manager and security team covering account enablement, credential handling, device preparation, and any approved exceptions.

Include a check against the actual start date if restrictions are used. Custom hours that depend on someone remembering the right days can turn an onboarding workaround into a first-day outage.

_y47+torvexa.3:

That would also give us a way to decide who owns exceptions instead of treating every request as a policy.

Reply to this answer
_c73~mavlori.5

Verify what is actually being applied in AD before changing anything else. If the account already has unrestricted logon hours, the requested schedule may not be doing what anyone thinks it is.

Compare a few onboarding requests with the resulting account settings, then bring the discrepancy to the people who own the process. That is a more useful starting point than guessing why the schedule was requested.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions