Adding the Step
Towards the end of your task sequence, add a Run Command Line step.Option A — Fixed/Manual Description
cmd /c net config server /srvcomment:"Finance Dept Laptop"
Option B — Dynamic via a Task Sequence Variable
If you’re capturing information earlier in the task sequence (for example via an HTA prompt) into a variable like%MachineOwner%, reference it directly:
cmd /c net config server /srvcomment:"%MachineOwner%"
Verifying It
Once the build completes, the description shows up in Computer Management > System Tools > Shared Folders and in network browsing views. You can take this a step further by also writing the same value back into the Active Directory computer object’s Description attribute during the task sequence, so it’s visible directly in ADUC as well.Still Current (Updated for 2026)
net config server is one of the older command-line utilities in Windows, but it remains present and fully functional on current Windows 10 and Windows 11 builds — it hasn’t been deprecated or replaced, so this task sequence step works unchanged today. The same approach also works with any other task-sequence variable you’re already capturing earlier in the sequence, not just %MachineOwner% — department, asset tag, or cost-centre codes are common alternatives to feed into the same /srvcomment switch.
Resources
Gear We Recommend
Testing configs is easier with a dedicated admin machine set up right. Here’s the kit we use.
Browse our Windows Admin Toolkit picks on AmazonAs an Amazon Associate, TechyGeeksHome earns from qualifying purchases.
Discover more from TechyGeeksHome
Subscribe to get the latest posts sent to your email.