I needed a script that would replace the user-specific information for each user, in this case, replace the user's name, job title, department, email, office and phone number. html file) with placeholders stored on a shared location accessible by all users:
I got the new email signature and I had to create a template so that my PowerShell script would fill in the information later. I quickly came up with a plan, develop a PowerShell script, that could copy the signature to the user's workstation, and have it run every time a user logs in. So it was clear to me Group Policies was the way to go. If you want this signature used for all messages including replies, click the Replies/forwards. Type (or copy/paste) your signature and click Save.
Let me set the scene here, I was working in a network with about 400 Windows workstations, and most of the infrastructure was Windows based as well. Type a name for the signature such as 'Default', and click OK. So how do you deploy a new email signature for all employees? Do you just send them an email, and have them do it themselves? Well, that's an option but then you would have to handle the unstoppable help requests from the less tech-literate employees. One of the targets for the rebranding was, of course, the corporate email signature which most of the 400+ employees were using. A few years back I was working as a SysAdmin for a big company, which was going through a rebranding process.
0 kommentar(er)
