At the beginning, we have to create a docx file. This is a normal file, containing a signature design as you want to appear and all variables from the script that you want to change (look at the end of the post for more information). This file has also to be saved on a share, where all the effected users have a read permission.
The script is written to create an Outlook signature and it is working if you have installed MS Word 2013 and MS Outlook 2013. It has been developed from a basic script on the Technet, but with additional checks and conditions as variables:
- $SignatureVer – A version of signature – Change it when you have to deploy a new signature;
- $UseSignOnNew – Use this signature when you send a new mail;
- $UseSignOnReply – Use this signature when you send a mail as reply;
- $ForceSignatureNew – Force this signature on a new mail. The user will not be able to change it (it will also force it on reply);
- $ForceSignatureReply – Force signature on reply to mails.
Be careful because using forcing signature, will create registry values. Cancelling these settings means that you have to delete manually the registry values.
Two new registry values used by the script are introduced:
- In the Path HKCU:’\Software\Microsoft\Office\15.0\Common\MailSettings, in the value VersionSignature, it is written a current version of the installed signature.
- In the Path HKCU:’\Software\Microsoft\Office\15.0\Common\MailSettings, in the value ADChangeDate, it is written the date when the signature was applied.
We need both values to determinate if the company changed the version of signature and the new one has to be deployed in addition if something changed in AD user object, since the last deployment of the signature. If the AD user was changed, the user can choose if deploying the changes or not (reason / example: AD User will also change if the user changes the password and we do not deploy the new signature).
The script should be run as a logon script and it is divided into two blocks:
- The purpose of the first block is to determinate if the signature has to be deployed to user. Here we can see if the user already has a signature deployed and if something has changed from the last deployment. This block query AD User object and compare data from AD with local data.
- The second block effectually deploys the signature and for the optimization of the speed and load it run only when the script has to be deployed. It copies the docx template to local machine, changes the variables with real data and generates the signature in Outlook. To do this, the Outlook will be closed if it is open. At the end, the script writes the two registry values and delete the signature template from the local machine.
The script does not delete or effect in any other way none of the signatures that are present in Outlook. The only effect will be that, if you select, it will change the default signature on new and / or reply mails. Of course all data of the AD User object can be retrieved; you just need to found a field name in AD and associate it with variable in the script. It is pretty easy.
In my script, there are some variables that have to be present in a docx template:
- DisplayName – Will be changed to Display value from AD
- E-Mail – Will be changed to E-Mail value form AD
- Title – Will be changed to Title value from AD
- AllAddress – Will be changed to complete address from AD (street, city, CAP)
- MobileN – Will be changed to Mobile number value from AD
- WorkingOffice – Will be changed to Office value from AD
Of course is up to you to change these values to any other value as you wish, but be careful that values defined in script, are presented the Word template document. Only in this case the script will be able to change them.
You can download script here: Mail_Sign script.
For any administrator, who want to use any kind of free tools to have better access or monitor some functionalities in Windows environments, here we have a list of many free tools. Just look which is usable for you and use it:
And please, test it in test environment prior you use it in production. Many times tolls are not exactly the same as you expect..
Do you have problems to deliver mails to Gmail or Hotmail?
I had some issues in last few months and at the beginning I was not able to solve the problem, because all the setting appears to be correct and I was not blacklisted (yes, I know that Google and Hotmail use their blacklist).
The question was how to reach the administrators on the destination side. To do this, just follow this links:
For Gmail: http://www.rackaid.com/resources/gmail-blacklist-removal/
For Hotmail: http://www.rackaid.com/resources/hotmail-blacklist-removal/
Here you will find a lot of information and the ticket to request the support.
PS: Maybe it is not a bad idea to check your status before you send the ticket. You can do it here: https://www.senderscore.org .
Microsoft published a new tool for managing Exchange Activesync functionalities. The tool is dedicated to administrators who wants to manage the process of remotely erasing mobile devices, list all devices for all users and many other functionalities. It is work on Office 365, Exchange 2010 and Exchange 2013
You can download it form here..
Move the FSMO Roles from SBS Server
At this point the SBS Server holds all five FSMO. In order to demote the SBS Server, these roles must first be moved to another domain controller. They can be safely moved to any Domain Controller in the domain.
To transfer the FSMO roles, follow this steps:
- Click Start, click Administrative Tools and then click Active Directory Users and Computers.
- If you are logged on SBS Server, right-click Active Directory Users and Computers and then click Change Domain Controller. If you are logged on the destination DC, you can go directly to step 4.
- In the Enter the name of another domain controller box, type the name of the server you want to transfer the roles to and then click OK.
- In the console tree, right-click Active Directory Users and Computers, point to All Tasks and then click Operations Master.
- Click the PDC tab and then click Change.
- Click OK to confirm that you want to transfer the role.
- Repeat steps 5 and 6 on the Infrastructure and RID tabs.
- Click Close to exit the dialog.
- Click Start, click Administrative Tools and then click Active Directory Domains and Trusts.
- In the console tree, right-click Active Domains and Trusts, point to All Tasks and then click Operations Master.
- To change the Domain naming operations master click Change and then click Close.
- Next, open an elevated command prompt and type the following command: Regsvr32 %systemroot%system32schmmgmt.dll
- Click on Start, click on Run and type MMC.
- In the MMC window click on File and then click on Add/Remove Snap-in…
- In the Add or Remove Snap-ins dialog click on Active Directory Schema, click Add and then click OK.
- Click Change Active Directory Domain Controller…
- Click to choose another DC in your forest and then click OK. Click OK to dismiss the warning dialog.
- Right-click on the Active Directory Schema and click Operations Master…
- Click the Change button. Click the Yes button when prompted to change the Operations Master.
- At the command prompt, type netdom query fsmo to verify that all the roles are now held by domain controllers, other than the SBS Server.
Uninstalling the Exchange Server
Now is time to uninstall the Exchange server from the SBS Server. Be careful, if you have installed ForeFront for Exchange Server. In this case you must first uninstall this product:
- Logon to SBS Server as Administrator.
- Click Start, click Run, then type Services.msc.
- Stop all the Exchange services.
- Click Start, click Control Panel, then select Programs and Features.
- Found Microsoft ForeFront Security for Exchange Server (if it is installed). Click Uninstall.
- Uninstall Microsoft ForeFront for Exchange Server.
- Restart the SBS Server.
The second thing that you must do is to create the registry key that enables you to remove the Exchange Server management tools:
- Click Start, click Run and then, in the Open text box, type regedit.
- Browse to HKEY_LOCAL_MACHINESoftwareMicrosoftExchangeV8.0AdminTools.
- From the Edit menu, click New and then click String Value.
- Type Type the name ConfiguredVersion.
- DoubleClick ConfiguredVersion and then, in the Value Data field, type the same value as the data value for the UnpackedVersion registry key, which is located in HKEY_LOCAL_MACHINESoftwareMicrosoftExchangeV8.0AdminTools.
- Close the registry Editor.
It could happen that you will also have to change manually the responsible server for OAB generation, remove public folders and change the source server for send connectors. This are the steps to control (change) this settings:
- To Change the source server for Send connectors:
- Click Start and then click Exchange Management Console.
- In tree view, on the left side, expand Organization Configuration, Hub Transport.
- In the result pane click Send Connector, then right-click on Windows SBS Internet Send connector and select Properties.
- Go to Source server tab and click Add…
- Select new Exchage server and click OK.
- Remove the SBS server from the list.
- Repeat the procedure for all the send connectors.
- Move the Offline Book generation to a new Exchange server (in case, that you don’t want to use public folders anymore, you must delete and create a new OAB).
- Open the Exchange Management Console.
- Expand Microsoft Exchange, expand Organization Configuration and then select Mailbox.
- In the results pane, click the Offline Address Book tab.
- On the Offline Address Book tab, select the offline address book you want to move. In the action pane, click Move.
- After the Move Offline Address Book Wizard appears, select the new server to host the offline address book generation by using the Browse button and then click Move.
- To close the wizard click Finish.
- Remove or move public folders. This steps are very clear explained on Microsoft Technet:
- For moving: http://technet.microsoft.com/en-us/library/bb331970(EXCHG.80).aspx
- For removing: http://technet.microsoft.com/en-us/library/bb201664(EXCHG.140).aspx
After this step, it is time to uninstall the Exchange server:
- Open Control Panel and then, in Programs, click Uninstall a program.
- On the Uninstall or change a program page, select Microsoft Exchange Server 2007 and then click Uninstall.
- In the Exchange Server 2007 Setup Wizard, on the Exchange Maintenance Mode page, click Next.
- On the Server Role Selection page, clear all of the server role check boxes and clear the Management Tools check box. Then click Next.
- On the Readiness Checks page, after the checks are finished, click Uninstall.
- On the Completion page, click Finish.
Demote the SBS Server and remove it from the domain
Log on to the Management Server as an administrator and follow this steps to remove the machine from the domain:
- Click Start, click Run and then type dcpromo.
- Click Next on the welcome screen.
- Click OK to dismiss the global catalog server warning.
- Click Next on the delete the domain screen. Do not select the delete the domain because this server is the last domain controller in the domain check box.
- On the Remove DNS Delegation page, verify that the Delete the DNS delegations pointing to this server check box is selected and then click Next.
- When prompted, type a password for the local administrator account. Click Next.
- Click Next on the review screen to begin the demotion.
- Click the Reboot on completion check box.
After the machine has finished rebooting, remove it from the domain following this steps:
- Log on to the SBS Server as an administrator.
- Click on Start, right-click on Computer, then click on Properties.
- Click on Change settings.
- Select the Computer Name tab and click Change…
- Select Workgroup under Member of and enter a unique value for the workgroup name.
- Click OK and reboot when prompted.
Log on to the DC Server and verify that the DNS A record and computer account for the SBS Server have been successfully removed.
Migrate from SBS 2008 or 2011 (Part 5).