- SBS 2008 needs a minimum of 3.2 GB Ram
- You cannot do an in-place upgrade of a sbs2003 machine to sbs2008, SBS2008 has to be installed on new hardware and if needed you can migrate data from sbs2003 to sbs2008 ( Wizard based procedure to do migration)
Reason: SBS2003 was only 32bit architecture, and SBS2008 is only 64bit architecture.
- With SBS2008, you can setup live internet address (Live A,MX records for your domain) via a wizard based procedure. Microsoft has partnered with Internet registrars such as [Go Daddy, etc]. In my opinion this would be a call generator too, imagine accountants calling in asking what are MX records. :D
- The only recommended (Supported) way of adding users and computers in SBS 2008 Is via its SBS Console, making users/computers directly in Active directory users and computers console is not supported, Reason: when a user is added via the SBS console, special Group policies, schema changes and tons of other power shell scripts are run against that user.
- Only the below predefined OU (Organizational units) are supported in SBS 2008,
OU= SBS USERS
OU= SBS COMPUTERS
OU=SBS SERVERS
ALL SBS 2008 users, computers and servers must belong to these OU's, if they are not in these OU, many SBS 2008 features are not going to work as designed.
- SBS 2008 may generate lots of certificate support calls, Main driver of this support calls would be some new features of SBS2008,
- Some of the Certificate related new features are:
RDP Over SSH
RWW Over SSH
Outlook Anywhere
With the above new features you can do a RDP, connect to network shares, open SharePoint, and connect to outlook all from the cloud using a secure connection without being connected to the LAN or being a part of a AD Domain, however all these features need Certificates to work..
- SQL/ SharePoint, there are a couple of Major differences between SQL/SharePoint 2003 and 2008.
- When we install SharePoint in SBS-2003 it use to make a new SQL SharePoint Instance, however with SBS-2008 it does not make any new SQL instances, INSTEAD it uses the MICROSOFT##SSEE instance for storing all SharePoint database's (this is a windows internal database engine)
With SBS-2003 if we needed to connect to SharePoint SQL instance we could connect via the instance name or the IP address of the sql server. However with 2008 the only way to connect to the windows internal database engine is via [Name pipes or shared memory]
- When we install SharePoint in SBS-2003 it use to make a new SQL SharePoint Instance, however with SBS-2008 it does not make any new SQL instances, INSTEAD it uses the MICROSOFT##SSEE instance for storing all SharePoint database's (this is a windows internal database engine)
- When we have communication issues, the first thing we usually do is shut down firewall from the services.msc console, however if you do that in SBS2008, the server would go into a complete block state, the supported way to shutdown firewall is via the native window firewall console.
- In sbs2008 you can only install Microsoft Signed drivers, beware of customers calling in for printer issues, lots of printers use un-singed drivers which will no longer work.
- Since SBS2008 is only 64 bit, Client computers which are 32 bit will have trouble connecting to a 64 bit print driver , Solution, on sbs2008 you can add a additional driver (32 bit) in the printer itself.
- Finally there is wizard available to move SharePoint database and Exchange Database files to a different location. However guess what, the wizard does not move Exchange or SQL Log files!!! Strange.
- SBS Server 2008 Premium comes with 2 server licenses; the 2nd server license is a windows standard 2008 license, Purpose of providing a separate server license is to segregate line of business applications (Exchange, SQL, Terminal server) into separate machines for better performance.
- You cannot configure a terminal server on the main SBS server, it has to be configured on a 2ndsbs2008 server (Provided you have a premium edition)An interesting FACT!!
Since most of the SBS goodies (RDP, RWW, OWA, and OUTLOOK Everywhere) is dependent on port 443, you need to make sure port 443 is routed to your server properly. Or else none of the above is going to work properly, for some reason my system was not accepting port 443 connections, we tried all the usual stuff (reconfigure router, reconfigured ports, reboot, etc) with no joy.
Solutions:
Disable TOE (BROADCOM DRIVERS) & my system started accepting 443 connections; SBS Server started working as normal. !!! (Not Strange!)
Thanks
Huzeifa Bhai
No comments:
Post a Comment