Installation guide

Upgrading Servers from Windows 2008 R2 32-bit to Windows 2012 64-bit ShoreTel Server Installation

ShoreTel 14.2 Planning and Installation Guide 233

8. Reboot.

9. Copy the Shoreline Data folder (excluding the \Database folder) to a safe location and label the

version and build in the folder in which it is located. It is recommended that you copy off the server

to a safe location.

10. Restart the ShoreTel services by running the following command:

C:\Program Files\Shoreline Communications\ShoreWare Server\Scripts\

hq_shoretel-start-svcs.bat

11. Ensure that everything is up and running properly.

12. Reboot.

13. Pull off to a safe location the ShoreTel Director Installation files and any other files that you may

want to keep.

14. After everything is off the server, reboot and boot from the Windows 2012 64-bit CD-ROM.

15. Format the hard drive and install Windows 2012 64-bit.

16. Log in via the local Admin Account.

17. Adjust the NIC so that it has the same static IP and name that it did before.

18. Add the server to the domain (be sure that it is placed in an empty Organizational Unit (OU) with

Block Inheritance). No Group Policies should be applied. If Group Policies do need to be applied,

be sure that they have already been tested against ShoreTel.

19. Turn off User Access Control (UAC).

20. Ensure that all of the Application Server Roles and Web Server Roles are installed.

21. Install the SMTP Role under Features.

22. Set DEP to Windows Programs and Services.

23. Install all of the Windows updates approved to the date specified in the Build Notes for the build on

your system.

24. Disable Windows updates.

25. Disable Internet Explorer Enhanced Security.

26. Disable the pop-up blocker.

27. Copy your old Shoreline Data folder back to the drive where you want to install the software.

WARNING!

Do not install any Anti-Virus software or Network security software. The ShoreTel Server is a

Telephony Appliance. If you absolutely need Anti-Virus software or Network security software due

to security regulations, use KB16704 to configure this properly.