My company is running SBS2008/SBS2011/Essentials, but it has grown to the point where this no longer meets our needs (We have too many employees!) and/or the software is going out of extended support. What is the migration path off of SBS/Essentials?
So customer calls up saying exchange isn't working, and when he remoted in he could see all the services disabled.
All the exchange services, IIS, update, plus a bunch of others were all set to disabled state.
Apon changing to automatic they started again fine and now email works, but how they got into this state is the worry.
I believe, from something similar years ago, that in msconfig there is diagnostic startup, which might result in said services being disabled. Again though, after another 'normal' reboot, why wouldn't they revert back to normal? And, how would it have gone into diag startup in the first place?
Anyway, a few other people on google seem to have had the same problem over the years but no one has really found a solution. At this stage we aren't ruling out a virus however it is a server with almost 0 access to the web so doubtful.
And exchange 2007 8.1 (some 0s missing) on server 2008 SBS (windows server standard FE 2007 SP2)
We have shadow copy enabled on our Windows SBS 2008 server. Attempting to restore a file from shadow copy gave the following error-
The source file name(s) are larger than is supported by the file system. Try moving to a location which has a shorter path name, or try renaming to shorter name(s) before attempting this operation.
The filename has 67 characters, and it's shadow copy path is 170 characters. These seem to be under the NTFS limits (260?).
We tried-
- Copying to the shortest path possible (C:)
- Copying to the shortest path possible on both a client computer and the server itself
Is it possible to rename files in a shadow copy, before doing the copy? Any idea why the error is appearing despite the filename size appearing to be within limits?
Steps taken
- On local computer, go to shared folder on SBS server (via mapped drive), e.g. J:\Projects\Foo\Bar
- Right click on folder and select Properties
- Click on the Previous Versions tab.
- Select a shadow copy and click Open
- In newly opened window, select folder/file and press Ctrl-C to copy.
- Open a new Windows Explorer, and paste folder/file onto local drive.
Edit- (Un)fortunately, I am now unable to reproduce this error. The particular files causing the problem have since been deleted, and unable to recreate the error with other, similar files.
I have had some problems using hardware-RAID on a server. Now I'm planning to use the Windows Server built-in software-RAID-1 instead. The server will only be used for Business Administrations, so I don't need high performance. The operating system is Small Business Server 2008 and the server is HP ProLiant DL320 G6.
Are there any disadvantages by using the Windows Server 2008 built-in software-RAID for mirroring?
We installed a few new computers to the network, and all of them appear to be having the same issue in Application Event Log:
Windows cannot obtain the domain controller name for your computer network. (The network path was not found. ). Group Policy processing aborted.
These workstations can still log into the domain, but deployed software installs and such to network computers are not taking place for these machines.
Is there a likely cause to this? Again, these were brand new machines, same OS (Win XP Pro) as all others.