-
Recently Browsing 0 members
- No registered users viewing this page.
-
Similar Content
-
The Script Lab Office add-in is now Microsoft owned and is no longer an open sourced app
By John Callaham,
- microsoft
- script lab
- (and 3 more)
- 5 replies
- 2 views
-
- 0 replies
- 1 view
-
Microsoft Office LTSC 2024 preview starts in April; consumer version due later this year
By John Callaham,
- 5 replies
- 4 views
-
- 0 replies
- 2 views
-
- 0 replies
- 2 views
-
Question
aclarke_31
Afternoon Everyone,
Quick question. Some time ago we migrated from Windows Server 2000 to Windows Server 2008 R2.
We used Microsoft's migration tool to upgrade to the latest version of Windows Server.
As part of the migration, we re-domained 200 odd workstations with mainly Windows XP.
A few weeks after the systems had been migrated, Microsoft Word started crashing when saving document or failing to save in general. Slowly over time, this started creeping out to other workstations.
We've been trying to track down the problem for some time, but we keep on having to fall back to a workstation rebuild in order to resolve the issue with crashing. 8/10 time's this resolves the problem, but in some cases it doesn't.
We've also highlighted Microsoft Office's File Validation Tool and put the update on hold (using WSUS) at the moment as we have had performance hits because of this.
Has anyone come across this problem before as I'm a bit stumped at the moment.
The documents in question are being saved to Windows Server 2000 SP4 and its quite a heavily utilized server.
The thoughts I've got at the moment are as follows,
Because the workstations are in the Window Server 2008 R2 domain, I was thinking that maybe group policy is telling systems to try and use SMB v2 but failing and trying to fall back to SMB v1.
Anyone got any thoughts?
Thanks for any input.
Link to comment
Share on other sites
5 answers to this question
Recommended Posts