SOLUTION SBS 2. 00. SSL conflict with Default website and SBS Web Applications. We have just migrated from SBS 2. SBS 2. 00. 8. The migration finally completed last week. Most of the important things are working fine, but there are some niggly issues which are puzzling me, almost all to do with IIS and remote access. Once the migration had completed, both Default web site and SBS Web Applications were bound to port 4. SSL. This meant that one of the servers SBS Web Application would not start. There isnt a default Group Policy setting that will change this for you, but if you have a Windows 2008 or Higher Domain Controller you can deploy a registry. Purchase SSL Certificates from DigiCert Order Unlimited Wildcard SSL, Extended Validation and MultiDomain SSL Certificates with friendly Phone, Email, and Chat. Although it would not start, it was not too bad because our mobile devices mainly i. Phones were able to use activesynchdirect push presumably via the Microsoft Server Active. Synch virtual directory within Default Web SIte. We could also get OWA via https remote. However, since SBS Web Applications could not start we cannot get to anything else like RWW etc. When I investigated this I found various resources including some posts on here telling me that Default Web site should only be bound to port 8. Sure enough, if I remove the 4. I can then start SBS Web Applications. However, that instantly means I lose active. SynchDirect Push for our remote devices and I can no longer access OWA. It seems like a catch 2. SBS Web Applications that should replicate the activesynch and OWA functions in Default Web Site. Exchange 2007 is designed to be used with Unified Communications also referred to as SAN subject alternative name or multiple domain certificate.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |