The company that is about to invest a lot of money into our company is mandating that our financial company be relocated into their building.Most of our IT imprint is within AWS (Workspaces, EC2 insta.
#Quickboot no longer works windows
I work as a Sr Windows Admin for a financial company.
I'm not sure of a good/automated process, other than manually making a weekly task in Outlook to check if any alias accounts need to be deleted. We also need to document a process that determines how long these aliases need to be maintained on the deleted account names, before I can permanently remove them. The most likely would be the user getting a new account with a number after the name: This could cause some VERY nasty issues for me if this were to ever happen. and already sees the name as an alias in the system, I'm not sure what might happen. When our IDM system goes to automatically recreate the users email address. I also wonder what may happen it one of these users suddenly becomes re-employed again while this process is in effect. Might need to re-think a more proper shared account name when I go into production with this. The reply came back from the " That might throw some people off thinking it could be a SPAM message. I created a "this individual is no longer employed" automatic reply on the deletedusers account and sent a test email from an external account. Then waited for everything to sync with O365. Well, I created a " shared account and then added a previously deleted users name (no longer exists in Exchange or A/D) as an "Alias" to it.
0 kommentar(er)
