Monthly Archives: March 2005

You are browsing the site archives by month.

Cannot connect to Sharepoint

In the mailbox tonight [one last post....] Carl asks “ I couldn’t connect from outside the router to the SBS2003 through Sharepoint. From inside, everything works fine. I turned on port 443 and 4125 on the router. How do I troubleshoot this?“


And Carl…your email address wasn’t right so it bounced back…so I’m blogging back the answer.  Figure it’s more productive then sending the email I’d really like to send to the Windows Update team right about now anyway…..


Remember if standard….port 444 also needs to be open from the outside on the router for Sharepoint.


If Premium there’s a KB with instructions to get it to go through ISA…it’s also here in the blog.


And that’s it for the blog posts tonight folks…see ya tomorrow.


 

My apologies.

I’m an SBSer.  And I feel that I represent the SBS community to Microsoft.

I feel like I’ve let the community down today.

I didn’t represent you well enough to the Windows Update team.  I didn’t understand the impact of the ‘normal’ Windows 2003 service pack 1 was on our SBS boxes.  I didn’t follow the beta closely enough to fully understand that it would have impact.  I didn’t understand that a Service pack that has impact on our SBS boxes would be offered up to us top of the window in Windows Update today.

I let you down.  For that I apologize.

Going forward I’m going to make it my personal goal to ensure that the patching goals at Microsoft include a goal that if a service pack of any kind adversely affects us that it will be blocked in Windows Update and will not be offered up to you if you go to Windows Update[Update... the Service pack is no longer on Windows update -- Thank you Microsoft for being VERY agile and responsive]

Someone asked today how to set up a test network if all they had was a production one and you can [if you are a Microsoft partner...see why you want to be a Microsoft partner] get a subscription to the “Action pack” which is a bundle of software that would be perfect for a ‘test’ network.  But if you don’t have the time for that ask in the communities about how the patch is working on systems.  We’ll tell you.

This one should not be installed on SBS.


UPDATE – 4/2/2005 – Windows update no longer offers up SP1 to SBS boxes.   Thank you Microsoft for responding to our concerns. 


From Sean Daniel, Windows Small Business Server


There has been quite a few questions regarding Windows Server 2003
SP1 and it’s support on Windows Small Business Server 2003: I hope
this post will clear up any of the confusion here.  If you have
immediate questions, please feel free to follow up in the public
Microsoft Newsgroup at: microsoft.public.windows.server.sbs I will
attempt to answer your questions as best I can.

Windows Server 2003 SP1 is supported on Windows Small Business
Server 2003, but there are some known integration issues that are
resolved in the Small Business Server SP1 (available within the next
60 days).  With the Windows Server SP1 installed, you may encounter
the known issues and our recommendation is to:
a)      Be patient with the issue and wait for Windows Small
Business Server 2003 SP1
b)      Un-install Windows Server 2003 SP1, and wait for Windows
Small Business Server 2003 SP1, which includes Windows Server SP1

Furthermore, a KB Article will be written to further address these
issues, I will post it to the public newsgroup when it is available.

In the mean time here is the short list of the known issues:
-      Remote Access Wizard hangs when creating the connection
manager package
-      Small Business Server Change IP tool will fail
o      Change IP tool will continue to fail after un-install of WS SP1
o      Workaround: Remove WS SP1, disable DHCP, re-run CEICW
-      Power Users retain SharePoint Administration privileges even
after the role is changed to Reader
-      Re-Install of Exchange fails
-      Re-Install of Intranet component fails
-      Fax Services won’t start and the Fax Configuration Wizard
cannot be run after un-installing Windows Server SP1
-      DHCP service may not start after a restore

Please let me know if you have any further questions


 

Here’s how to install a Service pack

Here are Susan’s suggested items on how to install a service pack on SBS 2003


  • You don’t install it on a production system, middle of the day during lunch time
  • You don’t install it before a weekend
  • You don’t install it before testing it yourself
  • You don’t install it before waiting for feedback from others [Community ...check with the community before installing it]
  • You don’t install it when it’s Windows 2003 sp1 and we should wait for SBS 2003 sp1






UPDATE – 4/2/2005 – Windows update no longer offers up SP1 to SBS boxes.   Thank you Microsoft for responding to our concerns. 









Coming Soon: Windows Small Business Server 2003 Service Pack 1


Published: March 29, 2005


The worldwide rollout of Windows Small Business Server 2003 Service Pack 1 (SP1) will occur in the next few months. Visit this page in the next 60 days to download Windows Small Business Server 2003 SP1.


Experience the Enhancements to Windows Small Business Server 2003 Service Pack 1


Windows Small Business Server 2003 SP1 will improve on the security, performance, collaboration, and productivity benefits built into Windows Small Business Server 2003.


Windows Small Business Server 2003 SP1 will be comprised of the latest service packs and updates for Windows Small Business Server 2003 and its product components, including:


Microsoft Windows Server 2003 SP1

Microsoft Windows SharePoint Services SP1

Microsoft Exchange Server 2003 SP1

Microsoft Office Outlook 2003 SP1

Microsoft Windows XP SP2

Microsoft SQL Server 2000 SP4 (Premium Edition only)

Microsoft Internet and Security Acceleration (ISA) Server 2004 (Premium Edition only)


Also included are built-in and customized integration capabilities to ensure a smooth installation experience. Windows Small Business Server 2003 SP1 will be available in 18 languages: English, German, Japanese, French, Spanish, Italian, Chinese (Simplified), Chinese (Traditional), Korean, Dutch, Polish, Swedish, Portuguese, Brazilian, Hungarian, Czech, Russian, and Turkish.

5717D53E-DD6D-4d1e-8A1F-C7BE620F65AA

5717D53E-DD6D-4d1e-8A1F-C7BE620F65AA

Don’t know what that is? 

That’s the unique SBS 2003 GUID code for the SBS suite.  Do a search in the registry and you’ll find it in a couple of places.

I’m sure you know you have SBS 2003.  You are an SBSer right?  But right now Windows Update doesn’t know you are a SBS box.  It thinks you are a Windows 2003 box.  The good news is that it’s not coming down on Autoupdate [thank goodness for that], but the bad news is if you run Windows Update on a SBS box it will indicate that you need this.  You don’t.  Also watch out for SUS and make sure that the service pack isn’t approved.


UPDATE – 4/2/2005 – Windows update no longer offers up SP1 to SBS boxes.   Thank you Microsoft for responding to our concerns.  And sorry too to the WU team.. I know you know what SBS is but you know us gals in the heat of the moment..stuff pops out.  Thank you for your quick action and response.


Let me say this loudly

IF YOU ARE RUNNING SBS 2003 WAIT FOR OUR SBS 2003 SP1  – don’t install this when it shows up on Windows update like this:

Again, do not install this patch from Windows Update.


UPDATE – 4/2/2005 – Windows update no longer offers up SP1 to SBS boxes.   Thank you Microsoft for responding to our concerns. 


Note: Customers who have Automatic Updates enabled with automatic
download should be aware that Windows Server 2003 SP1 will be made
available through Automatic Updates (AU) as a High Priority update in
July 2005.

UPS, unexpected power losses and oh? Have you done this registry fix?

Services may stop abruptly when you shut down or restart a Windows Small Business Server 2003-based computer:
http://support.microsoft.com/default.aspx?scid=kb;en-us;839262


Jeff from TechSoEasy reminds me of a registry fix that we SBSers need to do.  He had an issue with unexpected power issues and now has a bit of a messed up server.  It reminded me that he may have needed to put in that registry fix. Now this will be in the SBS 2003 sp1, but for now, do this registry fix manually.


Just a reminder…DO NOT install Windows 2003 sp1 on your SBS box [even if Windows Update is offering it to you]

Windows 2003 SP1 RTMs…ours is still in the oven

For those of you running ‘normal’ Windows 2003, you can start testing on the SP 1 as it just ‘RTM’d….

For those of us on SBS 2003 remember

In addition, Microsoft is announcing that Windows Small Business Server 2003 Service Pack 1 will also be available to customers within 60 days.


I’m putting that in Bold and in Color because I missed reading it the first time.  [ummm...sorry Jerry!... I tell ya going blind]


So folks… ours isn’t ready yet.  Hang tight just a little longer.







Download details: Windows Server 2003 Service Pack 1:

Install Microsoft Windows Server 2003 Service Pack 1 (SP1) to help secure your server and to better defend against hackers. Windows Server 2003 SP1 enhances security infrastructure by providing new security tools such as Security Configuration Wizard, which helps secure your server for role-based operations, improves defense-in-depth with Data Execution Protection, and provides a safe and secure first-boot scenario with Post-setup Security Update Wizard. Windows Server 2003 SP1 assists IT professionals in securing their server infrastructure and provides enhanced manageability and control for Windows Server 2003 users.

Which includes
Security Configuration Wizard for Windows Server 2003:
This is actually a cool tool but we don’t need to run it on our SBS 2003 boxes as we’re very well tweaked just as we are right now.  Again for those on normal server, take a look at it. 

What versions of Internet Explorer are supported?

Understanding the Windows lifecycle policy (for all you IT Pros out there):
http://blogs.msdn.com/ie/archive/2005/03/29/403513.aspx


One last post before bed tonight… nice consise recap of what IE versions are supported on what platform.

Really we’re not shouting!

SOMEONE IN MY OFFICE LEARNED TODAY …oh sorry…


Someone in my office learned today that when she was Internal IMing the guy in the office and she used all CAPS [because you see in the tax software program she was using it's normal for us to use all caps] that she was shouting at him.


She didn’t know that there’s this ‘rule of online’ etiquette that grew out of email etiquette


Send an e-mail in all UPPER-CASE. Use of upper-case words is the equivalent of shouting in some one’s ear. ONLY use upper-case words when trying to make a point (such as I just did). Even at that, you should be careful with who you are exchanging messages.“


For your clients that are email newbies, you might like to let them know of these unwritten/written rules of online etiquette.  Obviously they don’t need to learn l33t speak or anything like that but just a nice friendly ‘here’s what others expect of you online” is nice.


 

How to Shutdown

Ever notice how there’s like four or five ways to do the same thing?


I posted about my Remote Web Workplace experience and wanted to know if there was a way to remotely shut down.  Matt posted in the comments “shutdown.exe” but there’s a couple more.


Handy Andy said Start> run> “shutdown -r“


For one, once I have that Control-Alt-End which is the remote desktop equivalent of Control-Alt-Delete [the infamous three fingered salute -- no relationship to David just happen to share the same name]…bingo, I have a button there that says “shutdown”. 



Duh.


Then Chad and Marina said, click on Start and Windows Security and sure ’nuff in a RDP session, Windows Security…which is the shortcut to the screen that gives you task manager, shut down, log off, etc. is right there. [Which is of course the same solution pointed out to me by Dave in the post that started this whole exercise in the first place  -- that once you RDP into a session either via RWW or onto a server, that the Windows Security shortcut is right there, just a mouse click away]



Learn something new every day!

The icons got a bit messy today

One of the issues with Remote Web Workplace and especially with the interaction with a dual monitor system is the reality of ‘letting go of static icon location”.


Take this morning for example, I went to log back into RWW and there’s a brief moment where there’s a black screen and a blinking icon as the desktop ‘takes back control’ from the closed remoted session….well.. it’s supposed to be brief anyway.  This morning it got stuck on that black screen and I had to do a hard reboot.  And man, did the icons on the desktop not like that one bit.


Now 1/2 of my icons are on the other screen.  Normally I fix this by going into display properties, pulling the display back to merely one screen and then reenabling the second screen.  That’s probably the one thing you really need to kinda get use to when dealing with dual monitors.


Get over the ‘My icons must be IN THAT EXACT SPOT”.  Get used to them kinda blowing up and moving around every now and then.


One other burning unanswered question that I had about RWW that is now answered [thanks to SuperG and Dave] is how to do a control-alt-delete on RWW.


SuperG:  Control-Alt-End


Dave:  Windows Security icon in the start menu that brings up the Control-Alt-Delete dialog.


Oooh I forgot to ask if RWW can be rebooted remotely. That’s another one of my questions.  Stay tuned.