Thursday, July 19, 2007

Tuesday, July 10, 2007

SBS 2003 RTM, we lay you down to rest


I found out today that our buddy, SBS 2003 without Service Pack 1, is being removed from the list of supported products today. Not to be confused with SBS 2003 with SP1, or SBS 2003 R2, which continue on for support.

This means that today is a great day to Upgrade to SBS 2003 Service Pack 1! It's free!

The full list of other products that will no longer be supported, and when is available on the Lifecycle Support Page.

Monday, June 25, 2007

The Small Business Server Tech Library is now Live!


Our writing team has managed to put together a technical library of documentation up on TechNet. The direct link is here.

Some key advantages include:

  • Access everything from one location: All SBS product documentation is now in one central location, easy for you to find!

  • Search content: Use the search tool to search for a term or phrase throughout the entire SBS product documentation library, KB articles, TechNet, and more.

  • Provide feedback: Use the voting tools to submit your feedback and add comments about the quality of the information.

  • Watch it grow: Because of your comments, we’ll update the content on a regular basis.

Enjoy the new content!

Wednesday, June 13, 2007

Windows Home Server Reaches RC!

For those of you who are anxiously awaiting the Windows Home Server RTM, we're getting close. RC was declared!

Here are some fancy news articles:
Beta News
Windows Home Server Reaches RC1
June 13, 2007

Redmond Magazine
Windows Home Server RC1 Released
June 12, 2007

Computer World
Microsoft unveils Windows Home Server RC1
June 13, 2007

OSNews
Microsoft Windows Home Server Release Candidate
June 13, 2007

DailyTech
Microsoft Pushes Out Windows Home Server Release Candidate
June 13, 2007

The Tech Report
Windows Home Server release candidate rolls out
June 13, 2007

Wired – Gadget Lab
Windows Home Server Leaves Beta Testing
June 13, 2007

The Digital Lifestyle
Windows Home Server Release Candidate
June 13, 2007

Monday, June 11, 2007

Another Sneak Peak into Cougar

So, it appears that you enjoyed my last post about where my next version of SBS is. Well, I was surfing (my email) and this handy link of what's coming in Windows Server 2008 appeared.

As you know, Cougar's base operating system is based on Windows Server 2008. Many (but not all) of the features that come with Windows Server 2008, are available in Small Business Server. I unfortunately cannot speak to which features appear, and which one's don't.

But hey, nothin' like another teaser eh? I feel like a movie trailer, except I can't show you all the scenes and make you not want to go out and see the full-feature! :)



Due to increasing number of free web hosting services, a new web hosting company is sprouting up on every corner. With the sue of internet phones, world has been reduced to nothing. The webmaster basically makes use of these facts in online marketing, from web design to the rest of seo work.

Thursday, May 31, 2007

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.

Thursday, May 24, 2007

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!

Wednesday, May 23, 2007

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.
-------------------------------

Sunday, April 22, 2007

Tuesday, March 27, 2007

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.

Tuesday, March 20, 2007

Friday, March 02, 2007

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.

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!

Wednesday, February 28, 2007

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!