Browse by Tags

I was going to include this in the book, but decided it was not quite the right subject matter, so I've decided to post it on the blog. SBS 2003 had a pre-defined tool for VPNs. The tool exists in SBS 2008 to produce the same tool, but you have to configure it by hand. This is covered in this blog entry here . If you are on a client machine and you need create a VPN connection, or you are a user and want to create a VPN on Windows Vista, follow this guide. Start at the Start menu . Press the Connect To button to start the process. You will be told that you are already connected to a network, but you will need to create a new connection. Do this by selecting the Set up a connection or Network option and press Connect . In the Choose a connection option screen, select the Connect to a workplace option and press Next . Now select Use my Internet connection (VPN) . The Internet address is that for your remote server. If you are using Small Business Server 2008 (SBS 2008) this will likely be "remote."...

This question has been asked many times and was once again asked today on an internal forum.  It is hard to come up with an explicit answer, but I feel I can give you some (personal, non-binding, your mileage may vary, please take with a pinch of salt and don’t sue me) opinions.  For SBS 2003 the non-scientific sizing appeared to go like this: “between 2 & 4GB of RAM, depending on number of users”.  I often saw a machine for around 25 users with 4GB of RAM and there was headroom. Disk – don’t buy 1.5TB disks, but don’t by 30GB either.  Buy largish and try to size data before you make the decision 1 CPU or 2, or perhaps more importantly, a box that can take 1 CPU or 2? The the time SBS 2008 arrived the difference in cost of a 2GB or 4GB box was trivial.  Now SBS 2008, if you want to be scientific about it would look something like this: Minimum specs are found at http://www.microsoft.com/sbs/en/us/system-requirements.aspx Think Windows Server 2008 for x users, plus Exchange sizing for...

In my last post on installing Hyper-V for my home setup I said I had a number of issues.  One was that the Hyper-V Manager kept on showing the error "Cannot connect to the RPC service, make sure your RPC service is running".  This turned out to be several issues. To start with my Hyper-V box is in a workgroup, so security is manually configured.  Then there is the connection ID security - by hand and finally there is the client setup too.  I spent a long time with John Howard's blog which got me the following commands for the Hyper-V server: netsh advfirewall set currentprofile settings remotemanagement enable netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable=yes netsh advfirewall firewall set rule  name="Remote Administration (RPC-EPMAP)" new enable=yes profile=domain netsh advfirewall firewall set rule name="Remote Administration (NP-In)" new enable=yes profile=domain netsh advfirewall firewall...

With SBS 2003 R2, some of the Windows Server 2003 R2 features were not included. I asked today where we were with SBS 2008 and the CPU, Memory and feature lists are, so I am told, the same. On the page http://www.microsoft.com/windowsserver2008/en/us/compare-specs.aspx it talks about the max number of procs, memory etc for Windows Server 2008 Standard. You should use these to represent SBS 2008, however, note SBS 2008 has it’s own minimum requirements. See below for the important points KEY: = Not Available = Available Specification Standard Enterprise X64 Sockets 4 8 X64 RAM 32 GB 2 TB Failover Cluster Nodes (Nodes) 16 Fault Tolerant Memory Sync Cross-File Replication (DFS-R) Network Access Connections (RRAS) 250 Unlimited Network Access Connections (IAS) 50 Unlimited Terminal Services Gateway 250 Unlimited Virtual Image Use Rights 1 4 The features of Windows Server 2008 that are in Standard Edition can be found here - http://www.microsoft.com/windowsserver2008/en/us/differentiated-features.aspx which should...