Hey! Where's my next version of SBS?

You wanna know about the next version do you? Well, Since our trip to New Orlean's a TS2 blog has popped up some public information.(here), I'd like to take the opportunity to publish similar information here.

Cougar is the code name for the next version of SBS. When the SBS team decended on New Orleans, some of the following information came out to the public. I wanted to make sure I shared so you could know what's going on with the next version.

1. Cougar includes Exchange 2007 which is x64 only, This means that Cougar will be x64 only.


2. Since Cougar is x64 only we can deduce some things just based on how the technology works. This means in-place upgrades from earlier versions will not be supported (x86 hardware cannot support x64 software). Since Chris Almida was also there to speak to migrations, and he is our man in charge of the migration he is not planning to provide an in place upgrade from x64 hardware (again, this makes sense since the OS is x86, and it cannot be upgraded to x64). There will be a migration too that will take you from your current SBS to Cougar on ANOTHER BOX. We are still working on this solution. (I had a meeting yesterday on this actually!)


3. The SBS Backup solution is being completely re-vamped. However, we have made the full switch, and the backup solution will no longer support backing up to tape. Using snapshot technology, the backups will be extremely quick using incrementals that can be scheduled as often as every 30 minutes. A copy of NTBackup will be able to extract files from the old SBS 2003 format, but no new data can be added. If tape is super important to you, start sizing up 3rd party backup solutions.


4. To date, we are not planning on changing the 75 user limit.


5. Cougar will need to be installed behind some kind of firewall and the single-NIC model will be the only mode. You must use a firewall in front of the SBS box, this can be a hardware router type item, or a software firewall such as ISA.


6. Cougar will be based on Longhorn server now officially called Windows Server 2008.

In addition to the points made in New Orlean's, I'd like to add my own. Cougar looks really really sweet! But then again, I am biased. :o)

Our Beta 1 is in the field with our MVPs (don't ask, they can't talk about it either!) and I'm already starting to contemplate an upgrade to Cougar at my house. Now I just need to find some x64 hardware.... hrm....

---

With cheap web hosting, today we have many more email marketing options. However, it is important that out web hosting service offers email hosting as well. If not, there is a not a lot the webmaster can do with the wireless internet.

---

Read More

Want to prevent people from using PSTs on your network?

You have Exchange for a reason, it stores your email, and you do diligence to back it up daily. The problem is those pesky users keep moving mail to their PSTs. Hard drives crash, laptops are lost and along with that, email.

Why not force your users to keep all of their mail on the Exchange Server?

Well, it's a simple Group Policy object for Office 2003 and Office 2007.The problem is, SBS 2003 doesn't allow you to send out Registry edits without building a template for it. Well, a company called DesktopStandard has you covered with their PolicyMaker - Registry Extension plug in to Group Policy! This program is free (with registration) and can be installed on your SBS 2003/SBS 2003 R2 box. And it's my understanding, this company is working closely with Microsoft to build it's tools.

Once you've got that handy program loaded, you'll have to work around a minor issue if you have IE7 installed. Make the following Registry Key change:
HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_OBJECT_CACHING
Create the REG_DWORD with the value of mmc.exe, and ensure the value is 0.

Once that's all finished, we're ready to create the registry keys. To do so, here are the steps:

1. Click Start, Administrative Tools, and click on Group Policy Management.


2. When the GPMC opens, right-click domain.local and click on Create and Link a GPO here...


3. Call the Policy something familiar to you, like Prevent PST Usage.


4. You'll now see what you just created in the list of GPOs, right-click it and choose Edit...


5. In the new gpedit MMC window that opens, under User Configuration, and User Settings, select the new node called Registry


6. In the right pane, right-click in some white-space and choose New, Registry Item.


7. On the new property page that opens, fill out the following:
   
   
   • Action: Create
   
   
   • Hive: HKEY_CURRENT_USER
   
   
   • SOFTWARE\Microsoft\Office\12.0\Outlook\PST\
   
   
   • Value name: PstDisableGrow
   
   
   • Value type: REG_DWORD
   
   
   • 00000001
   
   Similar to the following picture:
   


8. If you have any Office 2003 versions on your network, you'll want to also repeat the last step, but make the registry key for version "11.0" instead: SOFTWARE\Microsoft\Office\11.0\Outlook\PST\

You will not see the two registry keys in the "Report" of the policy, in fact, the policy will appear to be blank! The reason for this is the report only shows items that have an .ADM template file associated with them. Registry keys do not.

On the clients, this registry setting will take place once Group Policy refreshes, you can force this by typing gpupdate /force from a command prompt window. You will be able to see these registry settings applied to the client by running the command: Start, then Run, then type in RSOP.MSC and hit ENTER. This command gathers the resultant set of policy and shows it for the machine you are on presently.

There you have it! This policy prevents the PST files from growing (hence writing to PST files) It does not prevent the user from loading up any PST file and reading mail out of it.

Gotta love the power of Group Policy!

Read More

How to launch a program always elevated under Vista UAC

This tip comes from our documentation team on how to launch a program that requires the use of some system files.

UAC is there for a reason, and I suggest only using this method if you know what you are doing and are ok with lowering the security level of your system!!

So now the warnings are out of the way, how do you create a shortcut that doesn't prompt you to run every time? Let's try creating one for the command prompt in Administrator Mode. Although this proceedure can be used for any application that is naughty for writing data into a system location, or that doesn't have a shim built for it to catch the data and write it into a better location.

These steps will require you are running as a local admin, with UAC enabled

1. Start the Task Schedule from Start, All Programs, Accessories, System Tools, and finally click on Task Scheduler


2. Accept the UAC prompt for running the Task Scheduler


3. Click Create Task... (be careful not to click Create Basic Task)


4. On the General, enter a Name and description, and ensure the Run with highest priviledges is checked similar to the following screenshot:
   
   
   
   Ensure you copy the name into the clipboard as you will need it later when building the shortcut.


5. Leave the Triggers tab empty


6. On the Actions tab, ensure you set an action to start a new program:
   
   
   • Ensure Action is set to Start a Program.
   
   
   • Browse to the path of the program, in thise case c:\windows\system32\cmd.exe.
   
   
   • Click OK
   
   Similar to the following screenshot:
   
   


7. On the Conditions tab, uncheck all the boxes.


8. On the Settings tab, make sure only Allow task to be run on demand, and If the task is already running, then the following rule applies is set to Do not start a new instance


9. Click OK


10. Right-Click on the desktop and choose New, Shortcut from the context menu.


11. When it asks for the location of the command, type in schtasks /run /TN "Command Prompt in Admin Mode". Please note that "Command Prompt in Admin Mode" is the exact string name of the scheduled task you created and copied above, similar to the following screenshot:
    
    
    And then follow through the rest of the wizard with whatever friendly name you want for the shortcut

Now each time you click on this icon, the command prompt will open in admin mode without prompting for UAC.

Again, I recommend if you can deal with the UAC prompt, you do so! This should be used as a last resort for those customers who can't handle the prompt because they open the application 100s of times a day.

-------------------------------
A cheap web hosting may mean more to spare on advertising, but compromising on the hosting means compromising on features like internet phones and online backup. In search engine optimization, it is important that domain registration is followed by the website design. Naturally for all this to happen, the hosting should be reliable.
-------------------------------

Read More

Want to use Remote Desktop to Span Monitors?

Today's tip comes from one of the writers on the SBS team. Thanks Stephen!

To make your Remote Desktop connection span multiple monitors, try this command line:
"mstsc %nameOfPc% /span"

Hope this helps!

Read More

Interested in Conserving a Little Power?

By default, in the Small Business Server - Windows Vista policy GPO, Specify the System Sleep Timeout (Plugged in) and Specify the System Hibernate Timeout(Plugged in) are set to Enabled to support Remote Desktop Connection. These settings ensure that, if the client computer that is running Windows Vista is plugged in, it does not enter the sleep or hibernate modes. This enables network users to access client computers that are running Windows Vista remotely.
If you want to optimize for power management instead of for Remote Desktop support, you can disable these Power Management Group Policy settings and configure Windows Vista to use Wake-on-LAN (WoL). WoL wakes up a computer that is running Windows Vista and prevents it from sleeping or hibernating when a remote connection is made. See the computer manufacturer's documentation to learn more about how to configure Wake-On-LAN settings.

To disable Power Management settings in the "Small Business Server - Windows Vista policy" GPO for all client computers running Windows Vista

1. From a client computer that is running Windows Vista, click Start, and then type gpmc.msc in the search box. A couple notes about this:
   
   
   • Be sure to log on to the Vista computer that is joined to the SBS domain and use the Domain Administrator account
   
   
   • When you log on to the Vista computer as the domain admin, you’ll need to specify your SBS domain name as part of the logon. For example, DOMAIN\Administrator.
   
   
   • On the Vista computer that you will use, It is recommended that you log off from any other user account on the computer (rather than using switch user) so that the policies are updated for all accounts at the end of the procedure.


2. In Group Policy Management Console, click Forest:DomainName, click Domains, click DomainName, and then click Group Policy Objects.


3. Right-click Small Business Server – Windows Vista policy, and then click Edit.


4. In Group Policy Object Editor, in Computer Configuration, click Administrative Templates, click System, click Power Management, and then click Sleep Settings.


5. In the details pane, double-click Specify the System Sleep Timeout (Plugged in).


6. Click Not Configured, click Apply, and then click OK.


7. In the details pane, double-click Specify the System Hibernate Timeout (Plugged in).


8. Click Disabled, click Apply, and then click OK


9. Close Group Policy Object Editor, and then close Group Policy Management Console.


10. To force the Group Policy settings to be applied (if you don't want to wait the 90-130 minutes for it to be applied), either run gpupdate /force from a command prompt with elevated privileges or restart the client computer. When you force the Group Policy updates, be sure to run the command elevated.
    
    
    • Click Start, type cmd
    
    
    • Right-click the Command Prompt icon in the Program files list, and then click Run as Administrator
    
    
    • Accept the prompt for UAC
    
    
    • Type gpupdate /force

Some additional points:

If you have modified the Power Management settings through Control Panel of the local Vista computer, log on to the account that you were using when you modified the Power Management settings

1. Open Control Panel


2. Select Power Options


3. For the power management setting that is currently in use, click Change Power Settings


4. Click Restore Default settings for this plan.

If you modified the Local Group Policy settings on the Vista client, you will need to clear any of those settings to return your Power Management settings to the default setting.

More information can be found here.

Now for the fun part!
An SBS MVP from Germany has created a Remote Web Workplace plug-in to allow you to Wake your PC up directly from the Computer Picker Page. Here's the trick. The site is in German, but the tool is native English (and only shows German text if the browser is German). Apparently he's open to adding your language if you should need it. Take this up with him.

So check it out at http://wol4rww.sbstools.de, and if you're like me, you may need some help with the webpage, which is easy with Babble Fish!.

---

Courses like 350-029 as well as 70-270 are hard enough and should follow 642-382 and VCP-310. This is important because without this, the student will not be able to comprehend a word about N10-003 or 350-029. This is the way IT training works.

---

Read More

Having Trouble with VPN after installing Server SP2?

This is a known issue with ISA 2004 and Windows Server 2003 SP2. Check out the potential solution over on the Official SBS Blog.

Read More

My RSS Feed

I've had a lot of complaints about my RSS feed either displaying always as the same date, or only partial posts. This morning I updated my feed links (to the right) to point to the Blogger recommended feed.... so if you're having one of these problems, try to re-subscribe using the new URL... Sorry for the inconvenience.

Read More

How to get more Familiar with SharePoint

Hi Folks,

I was recently asked if there was any way to try SharePoint before you actually configure it, to make sure you're getting the most out of the site on your SBS server.

Well, the TechNet folks have come through with a Virtual Lab that you can play with and get familar with the technology.

Hope this helps!

Read More

More (unsupported) methods of getting that self-issued cert onto WM5

So, over the past few days, I've ran into two more methods for getting that self-issued SBS certificate over to your mobile device so you can sync it against your server.

Method #1
Some mobile devices (and I say some, because I don't know why this is the case... yet), like the cert better if you export it as .DER encoded. You can go to your servers "certificate" store through mmc.exe and export the public cert as .DER encoded. It's possible this may install on your WM5 device. This one is actually supported, but may still be blocked by the security model on your phone.

Method #2
A friend of a friend of a friend of a friend used Bernt Lervik's method. I can't say it's a supported method, and as always, messin' around in the registry may wreck your device, but it just might work. I have not tried this method, and it may void support on your device from Microsoft or your provider!

And in other news. Windows Mobile 6 has released, you'll probably start seeing these devices around Christmas time. Looking to update your existing Windows Mobile 5 device? Keep your eyes on your provider and manufacturers websites.... and good luck!

Read More

Understanding the Flow of Mail through Exchange Anti-spam Architecture

I have to admit, I've been a little lazy in the blog posting, after spending all day writing specifications for the next version of SBS, I haven't got the fingers left to dance over the keyboard to share my knowledge with you. Plus of course, my knowledge is confidential (for the most part) at this time.

No, I don't wear an ear-plug and answer to the name of "Agent 3".

Anyways, looking at our specs for Exchange 12 anti-spam configuration, I came across something that's public, and will probably help you understand how the Anti-spam engine works on Exchange. This is of course for Exchange 2007, but most of it applies to Exchange 2003. The full article is available over on TechNet. But for the purposes of this blog, here's the meaty detail:

Read More

Need help with the new Daylight Savings Changes?

Check out the Microsoft Daylight Savings Time Help.

Read More

Configuring the Vista Firewall by Group Policy

Adding a Firewall rule in Group Policy to a Vista client is a little more difficult than Windows XP. It's not because it's harder, it's because there is no ADMX configuration file for the Vista Firewall.

But there is hope...

It is recommended that you only use this procedure to open the path for applications to connect through Windows Vista Firewall when you have installed the application consistently to the same program path across the network since this procedure applies to the entire domain. Alternatively, if you don't use the policy the user can accept the prompt at each computer when the application attempts to access the firewall.

1. From a Vista client (this is the main difference, you can't edit the policy from the server) connected to the domain, log on as the domain administrator


2. Open gpmc.msc


3. Navagate through your domain to the Small Business Group Policies


4. Right-click Small Business Server – Windows Vista policy (which will be available with the Vista Update coming soon), and then click edit. The Group Policy Object Editor appears


5. Computer configuration -> windows settings -> Windows Firewall with Advanced Security -> Windows Firewall With Advanced Security (no, this isn’t a repeat of the UI)


6. Right-click Outbound Rules, and then click New Rule


7. On the Rule Type page, accept the default of Program, and then click Next.


8. On the Program page, type the exact path used for installing the application on your client computers, for example, c:\path\program.exe


9. On the Action page, select the option to Allow the Connection


10. On the Profile page, select the types of network location that the rule will apply to (Domain, Private, or Public)


11. On the Name page, type a name and description for this program rule and the click Finish.


12. Close the Group Policy Object Editor and then close Group Policy Management

Note – to apply the policy immediately, you can run "gpupdate /force" using an elevated command prompt from the client

Why didn't the SBS team do this?
SBS didn't automatically configure the Vista Windows Firewall, because the new Vista firewall requires you to specify fully qualified paths to your installed applications. Since we have no way to know if you installed all the applications to the default locations, we chose not to open the firewall for applications that (1) may not exist, and (2) may be in a different location. Take extra care when creating such policies to not create exceptions in your client firewalls for applications that do not exist, or are installed in different locations.

---

Usually 642-432 and 642-825 are easy enough and do not require any background knowledge. However, if you plan to go for more than 642-825, maybe something like 220-601 or 70-290. it is best to cover 70-528 as well. Only then will you be eligible to go for mcse.

---

Read More

Check Out the Latest Microsoft Business and Technology Assessment Toolkit

On the SBS Usergroup tour, you learned about the Small Business Assessment Toolkit. Well, here is an update for you...

The new and refreshed toolkit (previously the Small Business Assessment Toolkit) can help you uncover opportunities across the Microsoft stack. New features include:

• Easy installation and self-updating features.
• New assessments that allow deeper evaluation of customers’ server, mobile, and desktop needs and help identify solutions using technologies based not only on Windows Small Business Server, but also on, Windows Mobile, the 2007 Microsoft Office system, and Microsoft Windows Vista.
• A customizable question bank that allows you to tailor assessments to your customers’ specific scenario or to the your own business model.
• A Windows-based platform that’s compatible with both Microsoft Windows Vista and the 2007 Microsoft Office system.

Assess and Win Free for Resale copy of SBS 2003 R2!
And while you’re using the toolkit, you can also get a free copy of Windows Small Business Server 2003 R2 Standard Edition (a US$599 value). Just use the toolkit to conduct business assessments with your customers and submit five assessments and complete a survey to qualify. And if you’re a Microsoft Small Business Specialist, you can also enter to win a Windows Mobile 5.0 Handheld Device as part of this offer.
Learn more at: https://partner.microsoft.com/assesssmbneeds

Read More

The Vista Update is Here!!!

The SBS Dev team has been working their buns off to get this update to you. Keep in mind that Vista could *always* join an SBS domain, just not using the http://server/connectcomputer website. You actually had to join the computer... manually.

And with any release that we work hard on, The SBS Team has put together this little blurb for you:

There has been a large amount of discussion in the community about the release of the Ripcurl update to allow Vista clients to participate in SBS domains (also known as the "Update for Windows Small Business Server 2003: Windows Vista and Outlook 2007 Compatibility (KB 926505)"). The updates you need are now available for download. (Yeah!)

Getting Started
First, start with the 31 page white paper. The white paper includes links to the downloads you need, as well as the manual steps you have to perform on the client and the server. The six downloads are:

• KB article 926505 - Update for Windows Small Business Server 2003: Windows Vista and Outlook 2007 Compatibility - http://support.microsoft.com/?id=926505.
• Direct download for the update - http://www.microsoft.com/downloads/details.aspx?FamilyID=9bf2f1e4-1b2c-471b-a284-e0c8c169fac3&DisplayLang=en.
• KB article 911829 - http://go.microsoft.com/fwlink/?LinkId=77013.
  • Enables OWA access from Vista clients.
• The User Profile WMI Manager - http://go.microsoft.com/fwlink/?LinkId=78007.
• Allows for local user profile migration.
• Needs to be installed manually on each Vista client before running Connect Computer.
• ISA 2004 SP2 - http://go.microsoft.com/fwlink/?LinkId=77017.
• Only needed for SBS 2003 Premium.
• Many customers will have this already installed. Also make sure that you have the latest ISA roll-up patch - http://support.microsoft.com/default.aspx?scid=kb.
• The ISA Server hotfix from KB 917902 - http://go.microsoft.com/fwlink/?LinkId=77019.
• Only needed for SBS 2003 Premium.
• The updated ISA 2004 Firewall Client - http://go.microsoft.com/fwlink/?LinkId=77006.
• Only needed for SBS 2003 Premium.

Notes, Highlights, and Gotchas from the White Paper:

• Windows Vista Business, Ultimate, and Enterprise are supported by the SBS Client Setup tools. You can connect Home SKUs manually, but it's going to be a lot of work. Since they can't join the domain, you'll have to manually enter passwords to access emai, file shares, web sites, etc. from any of the Home SKU clients.
• Older software will not, of course, be deployed to Vista clients. This includes older service packs, IE 6, ActiveSync 3.8 for all clients and Connection Manager in addition for 64 bit Vista clients.
• ActiveSync has been replaced by Windows Mobile Device Sync Center.
• If you have installed Office 2007, client setup does not install Outlook 2003.
• Office 2007 is not a free download. Vista clients that do not have Office 2007 installed will have Outlook 2003 installed.
• Don't attempt to install the SBS fax component on Vista. You will have to manually configure the Vista native fax client to connect to your SBS server. Steps will be posted on the Official SBS blog shortly
• A new GPO is added called Small Business Server - Windows Vista policy for Vista Firewall settings to allow access to resources on the SBS server.
• My documents redirection, if enabled, will automatically work with Vista clients, since Offline Files support is enabled by default in Vista.
  Remote Desktop is enabled by default and will allow connections from RWW to Vista client desktops.
• Power management is set to always on if the computer is plugged in (i.e. has a power supply) to ensure access via RWW. The white paper has steps on how to modify these settings if you want to optimize on Vista's power management features.
• Remote assistance only works Vista-to-Vista or from Vista to XP/2003 clients. Vista clients cannot request assistance from users on XP or 2003 machines. Use Remote Desktop instead for these scenarios.
• You will need to manually install the SBS cert on Vista clients that are not joined to the domain. The white paper has complete steps for how to manually import the cert.
• Bluetooth devices can cause problems with Connect Computer; disable them before accessing the site (i.e. attach a PS/2 or USB keyboard and mouse).
• After installing the hotfixes on the server, run gpupdate /force to make sure that policies will be applied to all clients.
• Spend some time with the troubleshooting sections at the end of the white paper- many known issues are covered there.

Didn't I tell you it was any day now? And I'm sure some of you didn't believe me.

Enjoy the Vista.

Read More