Why do you need to change the sid ?
You could push out the local security policy entry that renames the account, then update the users/users.local file w/ the new mapping and then reboot (I think you need a reboot for the policy to take effect)
THanks for the info - we found the security setting you referred to.
How do we go about making sure the machines have the correct ACLs? By default we provision these servers, with the Administrator account, and so have to have the exports file mapping to Administrator. So when we go to rename we need to make sure we push out the new Exports file, plus update the users and users.local -- but the users and users.local may get updated frequently.
Is there a best practice to follow here?
So in the same blpackage that pushes the setting I would have it:
- change the setting
- echo something into the exports or users or whatever file w/ the new mapping or push a file w/ the new mappings
- flag the blpackage as requiring a reboot and set the job to honor that reboot setting
Assuming you are mapping roles to a property you’d then need to update the mapping property (ADMIN_ACCOUNT?) and run the acl push job.
I am working with Robert on this, and cannot figure out how to flag the blpackage for a reboot. Can you let me know how?
1 of 1 people found this helpful
Highlight the item you want to trigger a reboot. On the right pane in the blpackage editor there will be a bunch of name values. single-user mode, reboot, etc. click on the value of the reboot item and change the dropdown to what you want.
Got it, thanks!!