Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DST woes...everybody on network fine...except me!!! 2

Status
Not open for further replies.
wahnula

wahnula

Technical User
Jun 26, 2005
4,158
US
Hello,

Running SBS2003 Premium, 9 Win2K clients, 1 XP pro (mine). I updated all clients, then ran TZMOVE to update Public Folders as outlined here:


My Outlook 2003 Calendar, and mine alone, in Public Folders, is one hour ahead ON MY CLIENT ONLY. Others viewing the same calendar on their Win2K client see the times correctly. Other users Public Folders calendars appear correctly on my client.

I ran the KB931836 XP update first, then the TZMOVE Outlook Public Folder change from this client. I made myself Owner of the calendar file in Public Folder permissions first. Other calendars in Public Folders of Exchange view correctly on my PC, just not my own! My XP PC is showing the correct time of day, and the little marker in Outlook is in the correct spot.

The one difference from my PC to the others is when I open Outlook my calendar is showing up as a Shared Calendar, I figured that was a unique XP feature. I'm going to climb a tower with a high-powered slingshot soon...help me please before I make the evening news!

Thanks folks.

Tony
 
Sort by date Sort by votes
If it's just public folder data and if that folder is in your Public Folder Favorites, check to see if you have "Download Public Folder Favorites" checked in the Exchange Account Properties > Advanced Tab. Clearing Offline Items is done by right clicking on the folder > properties > Clear Offline Items.

If not, follow the steps outlined here:





Jeffrey B. Kane
TechSoEasy
 
Upvote 0 Downvote
Did you already run KB926666 on your server? I assume you have, from other threads. Other than that, I'd do what Jeffrey suggested, and try disabling your offline cache for Outlook.

Actually try logging on to your computer as another user and looking at your calendar, so you can see if the issue is tied to your system vs your profile.

ShackDaddy
Shackelford Consulting
 
Upvote 0 Downvote
ShackDaddy said:
Did you already run KB926666 on your server?
Click to expand...

Thanks guys for the replies. I tried to run the KB926666 patch but was told to the effect "this patch is only available on SP2, you have an older SP installed". I had just run WU last Saturday and thought it had downloaded everything it needed. Apparently not. There was a "Windows Server SP2" available when I ran WU a few hours ago. Upon reboot, I received the message "Windows was unable to start with the current settings. A previous configuration was used"

Tried to run KB926666 (isn't 666 code for the devil???) and received the same information "needs SP2".

Upon inspection of "Add/Remove Programs", the Windows Server SP2 was installed, along with KB931836 and KB924881 on the 10th, not today.

I did not receive that "unable to start" warning on Saturday. Any idea what's going on?

Tony
 
Upvote 0 Downvote
All,

I can post screenshots of whatever you'd like to see, just ask.

Tony
 
Upvote 0 Downvote
There is no Windows Server SP2 in existence yet. There IS an Exchange Server SP2 but that wouldn't come down over automatic updates.

So, I wonder what you installed??? Log into safe mode and uninstall whatever it was!

Then, run a SYSTEMINFO and post the results here.


Jeffrey B. Kane
TechSoEasy
 
Upvote 0 Downvote
You have to have Exchange SP2 loaded before KB926666 will load. SP2 is not a deal-breaker to load, as long as you haven't already installed and customized the IMF, so you should probably feel free to go ahead and get it loaded. I've installed Exchange SP2 on about 14 servers in the last couple of weeks without issues.

ShackDaddy
Shackelford Consulting
 
Upvote 0 Downvote

points to the installation I did either through WU updates or from the SBS SP1 CD set. I don't download and install things willy-nilly, that's why I have Auto-updates OFF. The "last used" date was 6/06, coincident w/ SP1 install.

Since it obviously does not belong to SBS I will remove it and report back.

Tony
 
Upvote 0 Downvote
Uninstalled the above, still received the warning "a previous configuration was used"


Code: 
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>systeminfo

Host Name:                 HAL3000
OS Name:                   Microsoft(R) Windows(R) Server 2003 for Small Busines
s Server
OS Version:                5.2.3790 Service Pack 1 Build 3790
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Primary Domain Controller
OS Build Type:             Multiprocessor Free
Registered Owner:          Dave
Registered Organization:   My Company, Inc.
Product ID:                74995-066-4232197-XXXX
Original Install Date:     8/24/2005, 8:43:26 PM
System Up Time:            0 Days, 0 Hours, 4 Minutes, 0 Seconds
System Manufacturer:       System manufacturer
System Model:              System Product Name
System Type:               X86-based PC
Processor(s):              2 Processor(s) Installed.
                           [01]: x86 Family 15 Model 5 Stepping 10 AuthenticAMD
~1608 Mhz
                           [02]: x86 Family 15 Model 5 Stepping 10 AuthenticAMD
~1608 Mhz
BIOS Version:              Nvidia - 42302e31
Windows Directory:         C:\WINDOWS
System Directory:          C:\WINDOWS\system32
Boot Device:               \Device\HarddiskVolume4
System Locale:             en-us;English (United States)
Input Locale:              en-us;English (United States)
Time Zone:                 (GMT-06:00) Central Time (US & Canada)
Total Physical Memory:     4,095 MB
Available Physical Memory: 3,460 MB
Page File: Max Size:       1,876 MB
Page File: Available:      787 MB
Page File: In Use:         1,089 MB
Page File Location(s):     C:\pagefile.sys
Domain:                    HAL3000.local
Logon Server:              \\HAL3000
Hotfix(s):                 152 Hotfix(s) Installed.
                           [01]: File 1
                           [02]: File 1
                           [03]: File 1
                           [04]: File 1
                           [05]: File 1
                           [06]: File 1
                           [07]: File 1
                           [08]: File 1
                           [09]: File 1
                           [10]: File 1
                           [11]: File 1
                           [12]: File 1
                           [13]: File 1
                           [14]: File 1
                           [15]: File 1
                           [16]: File 1
                           [17]: File 1
                           [18]: File 1
                           [19]: File 1
                           [20]: File 1
                           [21]: File 1
                           [22]: File 1
                           [23]: File 1
                           [24]: File 1
                           [25]: File 1
                           [26]: File 1
                           [27]: File 1
                           [28]: File 1
                           [29]: File 1
                           [30]: File 1
                           [31]: File 1
                           [32]: File 1
                           [33]: File 1
                           [34]: File 1
                           [35]: File 1
                           [36]: File 1
                           [37]: File 1
                           [38]: File 1
                           [39]: File 1
                           [40]: File 1
                           [41]: File 1
                           [42]: File 1
                           [43]: File 1
                           [44]: File 1
                           [45]: File 1
                           [46]: File 1
                           [47]: File 1
                           [48]: File 1
                           [49]: File 1
                           [50]: File 1
                           [51]: File 1
                           [52]: File 1
                           [53]: File 1
                           [54]: File 1
                           [55]: File 1
                           [56]: File 1
                           [57]: File 1
                           [58]: File 1
                           [59]: File 1
                           [60]: File 1
                           [61]: File 1
                           [62]: File 1
                           [63]: File 1
                           [64]: File 1
                           [65]: File 1
                           [66]: File 1
                           [67]: File 1
                           [68]: File 1
                           [69]: Q147222
                           [70]: KB867460 - QFE
                           [71]: KB886903 - QFE
                           [72]: SP1 - SP
                           [73]: KB870669
                           [74]: Q832483
                           [75]: KB917283 - Update
                           [76]: KB922770 - Update
                           [77]: Q927978
                           [78]: Q828026
                           [79]: Q828026 - Update
                           [80]: KB925398_WMP64
                           [81]: KB885492 - Update
                           [82]: KB889101 - Service Pack
                           [83]: KB890046 - Update
                           [84]: KB893756 - Update
                           [85]: KB896358 - Update
                           [86]: KB896422 - Update
                           [87]: KB896424 - Update
                           [88]: KB896428 - Update
                           [89]: KB896688 - Update
                           [90]: KB896727 - Update
                           [91]: KB899587 - Update
                           [92]: KB899588 - Update
                           [93]: KB899589 - Update
                           [94]: KB899591 - Update
                           [95]: KB900725 - Update
                           [96]: KB901017 - Update
                           [97]: KB901214 - Update
                           [98]: KB902400 - Update
                           [99]: KB904706 - Update
                           [100]: KB904942 - Update
                           [101]: KB905414 - Update
                           [102]: KB908519 - Update
                           [103]: KB908531 - Update
                           [104]: KB908981 - Update
                           [105]: KB910437 - Update
                           [106]: KB911280 - Update
                           [107]: KB911562 - Update
                           [108]: KB911567 - Update
                           [109]: KB911897 - Update
                           [110]: KB911927 - Update
                           [111]: KB912919 - Update
                           [112]: KB914388 - Update
                           [113]: KB914389 - Update
                           [114]: KB916281 - Update
                           [115]: KB917159 - Update
                           [116]: KB917344 - Update
                           [117]: KB917422 - Update
                           [118]: KB917537 - Update
                           [119]: KB917734 - Update
                           [120]: KB917953 - Update
                           [121]: KB918118 - Update
                           [122]: KB918439 - Update
                           [123]: KB918899 - Update
                           [124]: KB920213 - Update
                           [125]: KB920214 - Update
                           [126]: KB920670 - Update
                           [127]: KB920683 - Update
                           [128]: KB920685 - Update
                           [129]: KB921398 - Update
                           [130]: KB921883 - Update
                           [131]: KB922582 - Update
                           [132]: KB922616 - Update
                           [133]: KB922819 - Update
                           [134]: KB923191 - Update
                           [135]: KB923414 - Update
                           [136]: KB923689 - Update
                           [137]: KB923694 - Update
                           [138]: KB923980 - Update
                           [139]: KB924191 - Update
                           [140]: KB924496 - Update
                           [141]: KB924667 - Update
                           [142]: KB925454 - Update
                           [143]: KB925486 - Update
                           [144]: KB925876 - Update
                           [145]: KB926436 - Update
                           [146]: KB928090 - Update
                           [147]: KB928255 - Update
                           [148]: KB928843 - Update
                           [149]: KB929969 - Update
                           [150]: KB931836 - Update
                           [151]: KB872769 - Update
                           [152]: XpsEPSC
Network Card(s):           3 NIC(s) Installed.
                           [01]: DGE-560T Gigabit PCI Express Ethernet Adapter
                                 Connection Name: Network Connection
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.0.101
                                 [02]: 192.168.168.1
                           [02]: Broadcom NetXtreme Gigabit Ethernet
                                 Connection Name: Server Local Area Connection
                                 DHCP Enabled:    No
                                 IP address(es)
                                 [01]: 192.168.16.2
                           [03]: 1394 Net Adapter
                                 Connection Name: 1394 Connection
                                 DHCP Enabled:    Yes
                                 DHCP Server:     N/A
                                 IP address(es)

C:\Documents and Settings\Administrator>

After running Windows Update I saw:

Code: 
High-priority updates 
Microsoft Windows Server 2003


 
Windows Server 2003 Service Pack 2 (32-bit x86)
Download size: 0 KB , 0 minutes  (Downloaded; ready to install)  
Microsoft Windows Server 2003 Service Pack 2 (SP2) is a cumulative service pack that includes the latest updates and provides enhancements to security and stability. In addition, it adds new features and updates to existing Windows Server 2003 features and utilities. After you install this item, you may have to restart your computer.  Details... 

 
Windows Internet Explorer 7.0 for Windows Server 2003

So...???

I really appreciate the help.

Tony
 
Upvote 0 Downvote
ShackDaddy,

I know. I was scared when I read

TechSoEasy said:
There is no Windows Server SP2 in existence yet.
Click to expand...

I am downloading Exchange SP2 at this moment. Any idea why I got the "Windows cannot load the current configuration" warning? Maybe Exchange SP2 will fix that...[neutral]

Tony
 
Upvote 0 Downvote
UPDATE: Exchange SP2 is in, the warning message is gone. I chose to overwrite newer files w/ the SP2 files. I am in the process of backing up my Exchange database, then,the antichrist, kb6666.

Thanks for your patience. I hold my breath every time I reboot, I am a skittish admin in case you an't tell already.

And I have been vindicated by ShackDaddy about "Windows Server SP2" being a real product and not a foolhardy download. TechSoEasy, we all make mistakes, although why SBS is not listed in the products it applies to is a mystery.

Tony
 
Upvote 0 Downvote
UPDATE: Installed the 926666 patch (hereafter known as the 666), cleared Outlook cache, ran TZMOVE with my time zone selected, all is well. Good thing I did have to reboot the SBS box, as one of the RAID5 member drives failed S.M.A.R.T. test upon restart, needed to be re-seated and is now rebuilt and solidly seated.

I think I will do some real work now...and hold off on SP2 for a while. Before I do, I really need to clean that server out. It's been 3 months (I log everything) and this construction office is really dusty.

I cannot thank you guys enough for guiding me through this rough spot.

Tony
 
Upvote 0 Downvote
Glad we were able to pull you through, Tony.

I'd wait on SP2 for a while. Since Microsoft barely even announced it was coming, it doesn't seem to be particularly critical. Seems like more of a rollup at this point. I'm wondering how much of it has already been included in patches, or whether its mostly made up of hotfixes.

ShackDaddy
Shackelford Consulting
 
Upvote 0 Downvote
Sorry for my comment regarding Windows Server SP2. It came down without any warning whatsoever. Usually Microsoft will give a heads up for Service Pack releases. But it did apparently come out on March 13th.

It's been removed from the "High Priority" updates, but there is really no reason to not deploy it on an SBS as far as I can tell. I've installed it on a few systems without any problem whatsoever.


Jeffrey B. Kane
TechSoEasy
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

DTGMI
  • Locked
  • Question
WIN 10 Pro PC & Adding back to our Network
Replies
0
Views
549
DTGMI
DTGMI
mangentle
  • Locked
  • Question
What could be the potential causes if a Microsoft Windows Server is experiencing slow network!
Replies
1
Views
1K
gbaughma
gbaughma
nukeinfer
  • Locked
  • Question
Internet restrictions for isolated PCs in the Network
Replies
1
Views
580
mangentle
mangentle
DeepuM
  • Locked
  • Question
Web Response returned Web Exception : The underlying connection was closed error | Simphony & QS
Replies
0
Views
451
DeepuM
DeepuM
DrB0b
  • Locked
  • Question
Hybrid on prem AD with Azure AD
Replies
2
Views
361
DrB0b
DrB0b

Part and Inventory Search

Sponsor

Back
Top