Install Exchange 2016 on Windows Server 2016

Install Exchange 2016 on Windows Server 2016

Install Exchange 2016 – Hi everyone. I am back and I am installing Exchange 2016 on Windows Server 2016 (currently TP3) from scratch on a virtual machine.

So before the install:

VMWare Workstation 10

256GB SSD (let’s see how fast the install will be)

2016 TP3 iso downloaded from Microsoft. Click Windows Server 2016 Download.

40GB of free space

Exchange 2016 Enterprise. Click Exchange 2016 Download.

Step by step what happens in the video below:

  1. I create a Virtual Machine using VMWare Workstation. Preferably with the most resources like CPU and RAM that you can spare. Attach the downloaded Windows Server iso file to the DVD/CD.
  2. Start the VM and boot from CD which has the Windows Server 2016 iso attached.
  3. We choose Windows Server 2016 Technical Preview (Server with Desktop Experience)
  4. We configure a static IP and change the name of the server and reboot
  5. Once the server is back from reboot we install Active Directory Domain Services from Server Manager. Add Roles and Features
  6. Follow along the auto-selected Features as well
  7. After the installation has finished go to Server Manager and click on the flag and choose to Promote this server to domain controller
  8. On the wizard step 1, choose 3rd option. Add a new forest
  9. Type the domain name below. Root domain name:_______
  10. Select Forest and Domain Functional level – Windows Server 2016/Technical Preview
  11. Check the Domain Name System (DNS) Server
  12. Type in a Directory Services Restore Mode password
  13. Ignore the Warning for DNS delegation and go Next
  14. Type in a NetBIOS name. Example. If contoso.com, you can choose just contoso. Use the default one at best
  15. Recommended that you don’t change the AD paths in the next section
  16. If no errors and just warnings proceed with Install
  17. After the reboot log back in and copy over the Exchange installation files to your server
  18. Start the setup
  19. Go through the initial setup screen with Next, then choose Recommended settings (not that important choice, whatever you like) and go to Next.
  20. Choose Mailbox role and check “Automatically install Windows Server roles and features…” and click Next
  21. Recommended that you leave the default path of “C:\Program Files\Microsoft\Exchange Server\V15”
  22. Type in an Exchange Organization Name. Can be whatever you like. Do not check “Apply Active Directory split permissions”
  23. If you want malware protection leave at “No” and click Next.
  24. The prerequisites check starts. Once it finishes you should only have one Error for missing the Microsoft Unified Communications Managed API 4.0 64-bit. The rest should be warnings. Download the API from here.
  25. If you have problems downloading due to error in Internet Explorer “Your current security settings do not allow this file to be downloaded” go to your Internet Options in your Internet Explorer. Go to tab Security. Click on Custom Level and browse to Downloads and change from Disable to Enable.
  26. Download and Install the API. Retry the Readiness Check.
  27. It should be only warnings and the Retry button to be replaced by Install button. Click and sit back for an hour.
  28. Your Exchange should be installed now. Here are some tips
  29. Your Outlook Web App or Outlook on the Web, as it’s called in 2016 is on the same URL as before – https://localhost/owa and your Exchange Administration Center is on – https://localhost/ecp.
  30. For your email flow to be full you need to create a Send Connector. In your Admin Center, go to Mail Flow and then Send Connectors. Click + to create a new one.
  31. Put a name for it. For type – Choose Internet
  32. Leave it on MX record associated
  33. Address space – click + and only add * to the “Full Qualified Domain Name” field. This means that through this send connector your will be able to send to all the domains in the world 😉 Leave the cost at 1.
  34. On the next menu click + and add your own server
  35. There we go you should be having a start-up working Exchange Server 2016 from scratch !!!

And this is the video !

Install Exchange 2016 on Windows Server 2016

Upgrading from Evaluation to Standard on a Domain Controller – Windows Server 2012 R2

Upgrading from Evaluation to Standard on a Domain Controller – Windows Server 2012 R2

Very interesting scenario. We used the 2012 R2 Evaluation copy when it came out and 6 months later it was just about to expire and the machine would shutdown every 1 hour. Getting to know how to convert from Evaluation to Standard/Datacenter I quickly got overwhelmed by the “You cannot convert domain controllers”. Since my server was a DC and my only DC I had to play a bit in order to achieve the conversion. First I install a virtual machine with a normal standard 2012 R2. I install AD and promote it to a DC. I confirm that AD has replicated to DC2 and then I demote the original server. Before I demote it I make sure that I transfer all the master roles to DC2. Once all is done and the server DC1 is demoted I run the command to convert from Eval to Standard copy. After the reboot the command has run successful. Then I promote DC1 to domain controller again, I move all the master roles back to it, i demote DC2, remove it from the domain, delete it from AD and the migration completed successfully. So in this “conversion” video we have the chance to actually experience demoting and promoting of domain controllers and transfer of master operational roles. Enjoy.

Here are all the articles you may need in the process :

http://technet.microsoft.com/en-us/library/cc778806%28v=ws.10%29.aspx

http://technet.microsoft.com/en-us/library/cc755885%28WS.10%29.aspx

https://www.google.bg/search?q=netlogon.dns&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:official&client=firefox-a&channel=sb&gfe_rd=cr&ei=AbagU7HUKsXc8geYzoGQCg

http://www.experts-exchange.com/Software/Server_Software/Active_Directory/Q_26902640.html

http://blogs.interfacett.com/how-to-demote-a-domain-controller-dc-in-windows-server-2012-active-directory-domain-services-ad-ds

http://support.microsoft.com/kb/296882

http://technet.microsoft.com/en-us/library/jj574204.aspx

And the video

Moving or Deleting the SBS Monitoring database in SBS 2008

Moving or Deleting the SBS Monitoring database in SBS 2008

By default the SBS Monitoring database resides under

C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data

which can grow to more than 4GB of size. This can cause disk space problems on the server and there is no particular need of it to be on the system drive. Here are the steps to move it to another partition.

sbsmonitoring-database-location

Stop any backup you may be running in SBS 2008

  1. Now navigate to C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data
  2. Open the SQL Server Management Studio Express and connect to the SBSMonitoring database.SERVER\SBSMONITORINGsbsmonitoring-connection
  3. Now we have a couple of options based on what we want to do
    1. If we want to flush the database and start with a clean one of a normal size you can delete the SBSMonitoring.mdf and SBSMonitoring_Log.Ldf files. After they are deleted we need to replace them with the same database files but files but emptied. You can download them from here. This is all you need to do and can move to step 6.
    2. If we want to move the database to another partition and still use it, now that you have stopped both of the services mentioned above. Move the SBSMonitoring.mdf and SBSMonitoring_Log.Ldf  files to another partition.

Right click the database -> Tasks -> Detach. Click Ok to detach the database. If you receive this error : Msg 3701, Level 16, State 1, ServerName\SBSMonitoring, Line 1
Cannot detach the database ‘SBSMonitoring’ because it is currently in use.

Go to Services again and restart the SQL ( SBSMONITORING ) service. Click Ok and the database should detach now. Right click the Databases folder now and click Attach. On Databases to attach : click Add and browse to the new location of the database. You can now proceed to step 6.

  1. Now go back and restart/start the SQL Server ( SBSMONITORING ) service and Windows SBS Manager service

Checks ! You can always check if the changes you just did are working. Generate a report, email it  and see if everything works fine. If not use the following guide.

http://blogs.technet.com/b/sbs/archive/2009/07/14/sbs-2008-console-may-take-too-long-to-display-alerts-and-security-statuses-display-not-available-or-crash.aspx

Renew a self-signed SSL Certificate in SBS 2008

Renew a self-signed SSL Certificate in SBS 2008

Renew a self-signed SSL Certificate in SBS 2008. If you have an expired SSL Certificate, you would want to renew it. This is done in the SBS Console. More specifically Fix My Network Wizard (FNCW). Running it will bring up potential network issues. Note that it will always find some but you need to ignore them and take care of the certificate only.

fix-my-network

When the wizard displays it results. De-select everything but the “Self-issued certificate is expired

Renew a self-signed SSL Certificate in SBS 2008

Finish the wizard and the certificate will be renewed.

Renew a self-signed SSL Certificate in SBS 2003

Renew a self-signed SSL Certificate in SBS 2003

If you have an expired SSL Certificate, you would want to renew it. This is done in the CEICW ( Configure E-mail and Internet Conection Wizard) in the SBS Console. Open Server Management -> Internet and Email -> Connect to Internet. Go through the wizard and don’t change anything until you reach this state of the wizard.

Renew a self-signed SSL Certificate in SBS 2003

When you issue a new certificate choose Web server name to be the domain name of the company which corresponds to the MX Record. For example domain.com have an MX Record of mail.domain.com. Therefore type mail.domain.com for a Web Server name in the CEICW wizard. Once the Wizard Finishes the certificate is renewed.

Restore Missing SBS 2003 CALs

Restore Missing SBS 2003 CALs

Restore Missing SBS 2003 CALs. At times the SBS License store might revert back to the initial 5 CALs, therefore users will experience disconnects from the server expressed in unable to dial a VPN, make a remote session or open shared documents. The process of dealing with this is the following :

  • Confirm there is a license problems by checking the Event Viewer on the server. Events 221 and 222 from source: LicenseService should be logged stating :License usage for product <product> is nearing the maximum number of per server licenses purchased. Consult License Manager from the Administrative Tools folder for more information.
  • Go to the SBS Console and check the Licensing tab for liceneses purchased and max usage statistics

Installed Licenses: 5  Maximum Usage: 15

According to Microsoft there are 3 ways to restore the CALs:

Re-enter the CALs

Restore the Whole C:/Windows folder

Restore the Licenses if ever backed up ( here is how )

Here is the Microsoft KB Article on how to restore them :

The number of client access licenses may be reset to five in Windows Small Business Server 2003

Important ! However these solutions are mostly too critical to action. So there is another solution to the problem. SBS2003 licenses are kept in a file – Windows\system32 called lisctr.cpa. Microsoft actually keep an automatic backup of this file in another file called – autolicstr.cpa. Stop the License Logging service, rename licstr.cpa to licstr.cpa.old, copy autolicstr.cpa and rename it to licstr.cpa. Start the License Logging service and see check if the Licenses are restored.

Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable.

Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable.

Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable.

Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable. You might have this error all of a sudden when trying to connect to your SBS Server through Remote Web Workplace. It may appear sudden but it’s not at all. The issue is connected to your IIS Application pool settings. For example if you install some third-party web application, it may have
changed the 32/64 bit feature on your Application pool. So what to do :

1) Go to IIS -> Application Pools -> DefaultAppPool -> Advanced Settings -> Enable 32-Bit Application – > if it’s True , change it to False

2) Check other relevant application pools for the same setting – > SBS Web Workplace AppPool or SBS Web Applications application poool

All of the pools should run with Enable 32-Bit – False

Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable.

Here is a technet forum link : http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/901d761e-773a-4dd0-a122-59d554fc63d8

Installing Windows Small Business Server 2008 ( SBS 2008 )

Installing Windows Small Business Server 2008

installing small business server 2008

What is SBS ?

Small Business Server is an all-in-one solution where on a single server you have a standard Windows Server with a number of other Microsoft technologies like Active Directory Domain Services, Microsoft Exchange Server, Microsoft SQL Server, Sharepoint Services, WSUS 3.0 and other SBS-only functionalities.

Before installing SBS 2008 you should know the system requirements and try to follow them because SBS without sufficient hardware is slow and painful. You will need to take into consideration these 2 properties:

Hardware requirements

Physical memory

Minimum: 4 GB

Recommended: 6 to 8 GB

32 GB maximum

Disk space

60 GB

The rest is not really something you should consider if you are only testing and playing with SBS 2008. In case you need the full system requirements – Find them here.

Here is the video of the Installation: