@nerdydad said in AIM Shutting down:
Used trillian so that I could have AIM, yahoo messenger, ICQ, and MSN Messenger all tied into one app.
Ha I used Pidgin at my last job and was able to tie in my wife's AIM account and talk to her throughout the day. My old boss blocked Skype and several other websites. He would also always be watching and call the center if he seen you on your personal phone for too long. Glad I got out of there.
Just trying to get some feedback on a really useless non issue. So it's being thrown around at my new company that using numbers in the SAM account name for duplicate names makes some users feel "unimportant" or like a clone of another user. From my limited experience with scripting it makes more sense to drop the # in the name so I can easily cleanup AD. eg. John Smith (jsmith) James Smith (jsmith1). It's easy (at least to me) to append a 1 or 2 in Powershell while searching for users in AD to manipulate settings. However it seems like too much work to have to ask HR to add the middle name in the Excel report they produce. Just so I can change my code to reflect that middle initial if, in the case there is a duplicate name, that the valid user isn't changed or removed. I'm getting the opportunity to make the decision in how this plays out, but I seem to be getting some flak because I want to do it the most logical way I can think of for growth when it comes to automating this process. My question to all of you is three part.
My gut tells me to standup for my opinion and push the #'s in the case of duplicates. What do you all think?
-The Count
@Dashrender said in User naming convention:
@Count-Chocula said in User naming convention:
@scottalanmiller said in User naming convention:
@Count-Chocula said in User naming convention:
If it wasn't for the fact that they have NEVER moved disabled users and there's 261 of them....
Maybe start with cleaning that up
That's the goal! Next I'm moving to GP. Right now they have a logon script that installs every printer on the network. This is going to be a great place to grow I think.
Logon scripts eh? GPP for the win.
I plan on implementing this for the printers and shares. It's been a busy two weeks trying to learn position, policy, and people. My ultimate goal is to rid this network of the logon script and filter the access to security groups. If this is either too much work, or the wrong approach please let me know.
Ha-Ha-lairious! Where do you do put the straw? Great stuff seriously.
@scottalanmiller said in User naming convention:
@Count-Chocula said in User naming convention:
If it wasn't for the fact that they have NEVER moved disabled users and there's 261 of them....
Maybe start with cleaning that up
That's the goal! Next I'm moving to GP. Right now they have a logon script that installs every printer on the network. This is going to be a great place to grow I think.
