SBS 2008 Console crashing on Network tab

On a Windows Server 2008 FE (known as SBS 2008) I have a weird problem. The SBS Console crashes on the Network Tab. I've read a lot about this issue on the Technet forums, but have not yet come to the solution.
When I click on the Network tab, I get this error:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: console.exe
Problem Signature 02: 6.0.5601.8540
Problem Signature 03: 502b0c6b
Problem Signature 04: Console
Problem Signature 05: 6.0.0.0
Problem Signature 06: 502b0c6b
Problem Signature 07: f9b
Problem Signature 08: 29
Problem Signature 09: N3CTRYE2KN3C34SGL4ZQYRBFTE4M13NB
OS Version: 6.0.6002.2.2.0.305.9
Locale ID: 1043
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
The console.log
[13924] 140627.175033.5433: General: Initializing...C:\Program Files\Windows Small Business Server\Bin\console.exe
[13924] 140627.175035.2705: General: Console shown...
[13924] 140627.175037.7077: AdminTME: Committer: RunAsync TaskPurgeBadADObjects
[13540] 140627.175037.7297: AdminTME: AdminDataLink Running Task: TaskPurgeBadADObjects
[13540] 140627.175038.0347: AdminTME: Status: TaskId = TaskPurgeBadADObjects, RootTaskId = TaskPurgeBadADObjects, Success: True, Warning: False, Continue: True, Message:
[13924] 140627.175038.3288: AdminTME: Committer: Completed called
[13924] 140627.175038.3288: AdminTME: Committer: Committer Completed.
[13540] 140627.175038.3748: Security Plugin Infrastructure: SecurityManager : Initializing SecurityManager
[13540] 140627.175038.3748: Security Plugin Infrastructure: SecurityManager : Number of plug-ins discovered : 5
[13540] 140627.175038.3818: Security Plugin Infrastructure: SecurityManager : Loading plug-in file : C:\Program Files\Windows Small Business Server\Data\SHExtensions\Antimalware.xml
[11248] 140627.175038.4748: Exception:
An exception of type 'Type: Microsoft.UpdateServices.Administration.WsusInvalidServerException, Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has occurred.
Timestamp: 06/27/2014 17:50:38
Message: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.
Stack: at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
at Microsoft.WindowsServerSolutions.SystemHealth.UpdateServices.DataProvider.InitializeWSUSDataLayer()
at Microsoft.WindowsServerSolutions.SystemHealth.UpdateServices.DataProvider..ctor()
at Microsoft.WindowsServerSolutions.Console.Controls.ReportCard.ReportCard.GetUpdatesHealthInfo(LEDstates& ledState, String& reportDescription)
[13540] 140627.175038.8188: Security Plugin Infrastructure: SecurityManager : Adding feature Virus protection for file system from plug-in C:\Program Files\Windows Small Business Server\Data\SHExtensions\Antimalware.xml
[13540] 140627.175038.8208: Security Plugin Infrastructure: SecurityManager : Adding feature Spyware and other malware protection from plug-in C:\Program Files\Windows Small Business Server\Data\SHExtensions\Antimalware.xml
[13540] 140627.175038.8208: Security Plugin Infrastructure: SecurityManager : Loading plug-in file : C:\Program Files\Windows Small Business Server\Data\SHExtensions\ClientFirewall.xml
[13540] 140627.175038.8228: Security Plugin Infrastructure: SecurityManager : Adding feature Client computer firewall from plug-in C:\Program Files\Windows Small Business Server\Data\SHExtensions\ClientFirewall.xml
[13540] 140627.175038.8238: Security Plugin Infrastructure: SecurityManager : Loading plug-in file : C:\Program Files\Windows Small Business Server\Data\SHExtensions\E12AntiSpam.xml
[13540] 140627.175040.0950: Security Plugin Infrastructure: SecurityManager : Adding feature Spam protection for e-mail from plug-in C:\Program Files\Windows Small Business Server\Data\SHExtensions\E12AntiSpam.xml
[13540] 140627.175040.0950: Security Plugin Infrastructure: SecurityManager : Loading plug-in file : C:\Program Files\Windows Small Business Server\Data\SHExtensions\FSE.xml
[13540] 140627.175040.6840: Security Plugin Infrastructure: SecurityManager : Adding feature Virus protection for e-mail from plug-in C:\Program Files\Windows Small Business Server\Data\SHExtensions\FSE.xml
[13540] 140627.175040.6840: Security Plugin Infrastructure: SecurityManager : Loading plug-in file : C:\Program Files\Windows Small Business Server\Data\SHExtensions\WindowsFirewall.xml
[13540] 140627.175040.6870: Security Plugin Infrastructure: SecurityManager : Adding feature Server firewall from plug-in C:\Program Files\Windows Small Business Server\Data\SHExtensions\WindowsFirewall.xml
[11640] 140627.175041.3551: Antimalware Reporting: Thread ID : 9 : AntivirusHealthCheck : Number of clients detected : 11
[11428] 140627.175041.3781: Antimalware Reporting: Thread ID : 11 : AntispywareHealthCheck : Number of clients detected : 11
[13540] 140627.175041.4541: Security Plugin Infrastructure: ClientFirewallDetailGroup : Detected Firewall Status. Client : WP2013-01.nai.local, Status : Unknown
[13540] 140627.175041.4881: Security Plugin Infrastructure: ClientFirewallDetailGroup : Detected Firewall Status. Client : WP2013-04.nai.local, Status : Unknown
[13540] 140627.175041.4981: Security Plugin Infrastructure: ClientFirewallDetailGroup : Detected Firewall Status. Client : WP2013-11.nai.local, Status : Unknown
[13540] 140627.175041.5211: Security Plugin Infrastructure: ClientFirewallDetailGroup : Detected Firewall Status. Client : WP2013-05.nai.local, Status : Unknown
[13540] 140627.175041.5281: Security Plugin Infrastructure: ClientFirewallDetailGroup : Detected Firewall Status. Client : WP2013-09.nai.local, Status : Unknown
[13540] 140627.175041.5351: Security Plugin Infrastructure: ClientFirewallDetailGroup : Detected Firewall Status. Client : WP2013-08.nai.local, Status : Unknown
[11248] 140627.175042.1732: Antimalware Reporting: Client : NAI-001.nai.local, Thread ID : 6 : AntimalwareReport : Client is not in antimalware framework client list : NAI-001.nai.local
[11248] 140627.175042.1752: Antimalware Reporting: Client : NAI-001.nai.local, Thread ID : 6 : AntimalwareReport : Client is not in antimalware framework client list : NAI-001.nai.local
[3312] 140627.175042.5602: ClientSetup: Microsoft.UpdateServices.Administration.WsusInvalidServerException: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.
at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
at Microsoft.WindowsServerSolutions.SystemHealth.UpdateServices.DataProvider.InitializeWSUSDataLayer()
at Microsoft.WindowsServerSolutions.SystemHealth.UpdateServices.DataProvider..ctor()
at Microsoft.WindowsServerSolutions.Console.Pages.Computers.Computers.QueryCompUpdateJob.SetUpdateCompliance()
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
[3312] 140627.175042.5612: Admin: !!!!FATAL: Console shutting down due to unhandled exception: Exception has been thrown by the target of an invocation.
[3312] 140627.175042.5632: Exception:
An exception of type 'Type: System.Reflection.TargetInvocationException, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 06/27/2014 17:50:42
Message: Exception has been thrown by the target of an invocation.
Stack: at Microsoft.WindowsServerSolutions.Console.Pages.Computers.Computers.QueryComputerJob.OnCompleted(Object sender, RunWorkerCompletedEventArgs e)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
An exception of type 'Type: Microsoft.UpdateServices.Administration.WsusInvalidServerException, Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Culture=neutral, PublicKeyToken=31bf3856ad364e35' has occurred.
Timestamp: 06/27/2014 17:50:42
Message: Exception of type 'Microsoft.UpdateServices.Administration.WsusInvalidServerException' was thrown.
Stack: at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer()
at Microsoft.WindowsServerSolutions.SystemHealth.UpdateServices.DataProvider.InitializeWSUSDataLayer()
at Microsoft.WindowsServerSolutions.SystemHealth.UpdateServices.DataProvider..ctor()
at Microsoft.WindowsServerSolutions.Console.Pages.Computers.Computers.QueryCompUpdateJob.SetUpdateCompliance()
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
[12392] 140627.175042.6282: ClientSetup: NetGetJoinInformation (server = [WP2013-07], ...)
[12392] 140627.175042.7202: ClientSetup: NetGetJoinInformation (server = [WP2013-03], ...)
[14260] 140627.175042.7202: ClientSetup: Computer [WP2013-07] - JoinStatus: [NetSetupDomainName], DomainName: [NAI], Expect: [NAI]
[13732] 140627.175042.8162: ClientSetup: Computer [WP2013-03] - JoinStatus: [NetSetupDomainName], DomainName: [NAI], Expect: [NAI]
[12392] 140627.175042.8162: ClientSetup: NetGetJoinInformation (server = [WP2013-10], ...)
[12392] 140627.175042.8812: ClientSetup: NetGetJoinInformation (server = [WP2013-02], ...)
[13636] 140627.175042.8812: ClientSetup: Computer [WP2013-10] - JoinStatus: [NetSetupDomainName], DomainName: [NAI], Expect: [NAI]
[12392] 140627.175042.9392: ClientSetup: NetGetJoinInformation (server = [WP2013-06], ...)
[12296] 140627.175042.9392: ClientSetup: Computer [WP2013-02] - JoinStatus: [NetSetupDomainName], DomainName: [NAI], Expect: [NAI]
[11476] 140627.175042.9962: ClientSetup: Computer [WP2013-06] - JoinStatus: [NetSetupDomainName], DomainName: [NAI], Expect: [NAI]
[5720] 140627.175043.5143: ClientSetup: GetComputerStatus (WP2013-01.nai.local) SendPing false
[5720] 140627.175043.5163: CoreNet: ARPCanResolveIP called with null==source -- SendARP will have to determine the Nic
[14260] 140627.175044.0143: ClientSetup: GetComputerStatus (WP2013-08.nai.local) SendPing false
[14260] 140627.175044.0143: CoreNet: ARPCanResolveIP called with null==source -- SendARP will have to determine the Nic
[8804] 140627.175045.0144: ClientSetup: GetComputerStatus (WP2013-05.nai.local) SendPing false
[11136] 140627.175045.0144: ClientSetup: GetComputerStatus (WP2013-11.nai.local) SendPing false
[8804] 140627.175045.0144: CoreNet: ARPCanResolveIP called with null==source -- SendARP will have to determine the Nic
[12244] 140627.175045.0144: ClientSetup: GetComputerStatus (WP2013-04.nai.local) SendPing false
[12244] 140627.175045.0144: CoreNet: ARPCanResolveIP called with null==source -- SendARP will have to determine the Nic
[11136] 140627.175045.0144: CoreNet: ARPCanResolveIP called with null==source -- SendARP will have to determine the Nic
On the services.msc i see that the following services are not started:
SQL Active Directory Helper
SQL Server Agent (SQLEXPRESS)
SQL Server Browser
Windows Internal Database (MICROSOFT##SSE)
When i try to start the SQL Active Directory Helper, i get the following message:
Windows could not start the SQL Server Active Directory Helper on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -1073741724.
When i try to start the SQL Server Agent(SQLEXPRESS) and SQL Server Browser, i receive the following message:
The <SERVICE_NAME> service on Local Computer started and then stopped. Some services stop automatically if they are not in use by other services or programs.
When i try to start the Windows Internal database, i receive the error:
Windows could not start the Windows Internal Database(MICROSOFT##SSEE) service on Local Computer.
Error 1067: The process terminated unexpectedly.
The system log records the message:
Log Name: System
Source: Service Control Manager
Date: 27-6-2014 18:11:32
Event ID: 7034
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: NAI-001.nai.local
Description:
The Windows Internal Database (MICROSOFT##SSEE) service terminated unexpectedly. It has done this 5 time(s).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Service Control Manager" Guid="{555908D1-A6D7-4695-8E1E-26931D2012F4}" EventSourceName="Service Control Manager" />
<EventID Qualifiers="49152">7034</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-06-27T16:11:32.000Z" />
<EventRecordID>694617</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>NAI-001.nai.local</Computer>
<Security />
</System>
<EventData>
<Data Name="param1">Windows Internal Database (MICROSOFT##SSEE)</Data>
<Data Name="param2">5</Data>
</EventData>
</Event>
I have replace those folders, form an sbs server with the same OS where the console still works:
C:\Program Files\Windows Small Business Server\bin
C:\Program Files\Windows Small Business Server\Data
I think these services are related to WSUS and WSUS is related tot SBS Console. Do i have to re-install WSUS? reinstallation of WSUS on a SBS server, I think that is very risky. What do you think?
Sincerely, Martien van Dijk -------------------------------------------------------------------------------- Please remember to mark the replies as answers if they help and unmark them if they provide no help. Check out
My Blog!

Hi,
Sorry for my delay.
àWindows Internal
Database (Microsoft##SSEE)
àI think these
services are related to WSUS and WSUS is related tot SBS Console.
Based on those error messages, I will agree with your viewpoint. This issue seems to be related to WSUS.
On current situation, please refer to following operations and check if can help you.
1. Run
SBS BPA and check if can find some issues, then solve them.
2. Please refer to the following article and repair Windows Server Update Services, then monitor the result.
Repair Windows Server Update Services
3. If this issue still exists, please
repair SBS 2008 console and check if can help you.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Similar Messages

Excessive downloads by an SBS 2008 client bogging down network

Hello. I have been trying to find the source of a vexing problem on my Small Business 2008 network. It only seems to affect 2 computers and only while logged in. One of them is mine, a Windows 8.1 Pro client computer.
The bottom line is my computer is downloading, continuously from the server at two different levels. One I have lived with for a long time, where I my computer uploads and downloads from the server at 1.5Mbps.
The second, and more concerning, is where it downloads from the server at anywhere from 25-110Mbps. This occurs about 50% of the time. I run NetSpeed Monitor so I can track the traffic. This morning alone, it has downloaded over 320GB from
the server and we have a very small server with only 3 GB on the data drive. This is not a problem on most other stations in the network. Only 1 other computer, a laptop, has a similar problem on this scale and I leave it logged off for now.
I can't find any sign of malware on my client computer and scan regularly (with Kaspersky Small Office Security 3).
All of this network traffic is found under one process in both the client computer and the server, System PID 4. I can provide screen shots if it will help.
Our network performance with the SBS 2008 file server is poor and I think this is contributing.
Please let me know what additional information I can provide to help solve this problem. I tried Process Explorer, but that provided no useful info. I'm wondering if it's a rogue service.
The problem is not evident when I first login, but it appears within a few minutes.
Thank you for any suggestions to try,
Mike

I'm mostly getting these from WireShark:
258117
25.038883000
192.168.11.5
192.168.11.31
TCP
1514
[TCP segment of a reassembled PDU]
Source Port: 445 (445)
Destination Port: 54628 (54628)
(Hundreds of thousands of these per minute). 192.168.11.5 is the server and 192.168.11.31 is my workstation.

WSUA not connecting to server and SBS 2011 console Crashing when going to security/update tab

Running SBS 2011, all of a sudden the daily reports was not generated and the SBS Console would crash. If I uncheck the update option under report properties the report will run with out any issues. If the update option is checked the console will crash
with the following message:
When I open WSUS I get the following error:
Nothing has been changes on the server and no 3rd party antivirus software installed. Any Suggestions??

Hi BruceR80,
Based on current situation, please refer to the following articles, then repair the SBS 2011 Standard Console
and Windows Server Update Services. Please check if can help you to solve this issue.
Repair the Windows Small Business Server
2011 Standard Console
Repair Windows Server Update Services
In addition, please locate to:
c:\program files\windows small business server\logs folder. And check
Console.log file if you can find some error messages, please feel free to let me know.
By the way, please click
Start-> Run-> type Services.msc. In Services, please check
Windows Search service and make sure the Startup Type was set as "Automatic".
Hope this helps.
Best regards,
Justin Gu

SBS 2011 Console Crashes

Hi! Every time I launch the SBS Console it crashes immediately.
I've tried to repair the console via add/remove programs, and I've tried the steps outlined in both of these documents with no success:
https://technet.microsoft.com/en-us/library/gg680337.aspx
http://support.microsoft.com/kb/2616792
Any ideas?

Thank you. Here is the last entry in the log:
[10932] 150306.174717.3998: General: Initializing...C:\Program Files\Windows Small Business Server\Bin\console.exe
[10932] 150306.174717.8522: General: Console shown...
[10932] 150306.174718.0394: Admin: !!!!FATAL: Console shutting down due to unhandled exception: Initialization failed.
[10932] 150306.174718.0550: Exception:
An exception of type 'Type: System.IO.IsolatedStorage.IsolatedStorageException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' has occurred.
Timestamp: 03/06/2015 17:47:18
Message: Initialization failed.
Stack: at System.IO.IsolatedStorage.IsolatedStorageFile.Init(IsolatedStorageScope scope)
at Microsoft.WindowsServerSolutions.Console.Common.Persistance.IsolatedMementoStorage.Contains(String id)
at Microsoft.WindowsServerSolutions.Console.Pages.Page.LoadMementoCache(Guid guid, MementoStorage storage)
at Microsoft.WindowsServerSolutions.Console.Pages.Page.LoadCache()
at Microsoft.WindowsServerSolutions.Console.Pages.Home.Home.Initialize()
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at Microsoft.WindowsServerSolutions.Console.Program.Main(String[] args)

Windows SBS 2008 Deployment Report for Updates in SBS Console Is Empty

The SBS Console on my Windows SBS 2008 is able to report updates which are available for deployment, and it also is aware of the number of computers which are affected by the update in the Security>Updates summary page in the SBS console. However, if
I select an update and click "View the update deployment report," there are no computers listed.
I have gone through the steps outlined in these posts:
Repair monitoring and reporting features in Windows Small Business Server 2008
SBS2008: Windows SBS Console may crash because of incorrect Environment Variables
My variables read read TEMP=C:\user\me\appdata\local\temp\1 and TEM=C:\user\me\appdata\local\temp\1 from the command line, but in the Environment Variables window, they both read as C:\user\me\appdata\local\temp\
SBS 2008 Console May Take Too Long to Display Alerts and Security Statuses, Display Not Available, or Crash
(I was unable to run this from the command line, even though I was running the command as administrator, and had remote connections allowed. I ended up running this command in the SQL management studio.)
Repair Windows Update Services
I am sorry for the missing hyperlinks, but I am not allowed to post them until my account has been verified. Searching for the article titles in bold will take you to the referenced page. I thought it would be helpful to mention the steps I have tried to take
before taking to the forums with my problems.
Any ideas? Does this need any clarification?

I did take a look at the console. When I refresh the list under the Updates
tab in the Security ribbon, I get multiple lines of:
[11340] 140114.090516.2325: Update Services: GetConfiguration: level Medium is read from config file C:\Program Files\Windows Small Business Server\Data\sbsconfig.xml
[16772] 140114.090535.4166: Update Services: GetConfiguration: level High is read from config file C:\Program Files\Windows Small Business Server\Data\sbsconfig.xml
Then, every time I try to view the computers to which a particular update apply, the console throws these lines into the Console.log:
[8416] 140114.090659.3547: AdminTME: Committer: RunAsync TaskViewDeploymentReport
[21016] 140114.090659.3703: AdminTME: AdminDataLink Running Task: TaskViewDeploymentReport
[21016] 140114.090659.3703: AdminTME: Status: TaskId = TaskViewDeploymentReport, RootTaskId = TaskViewDeploymentReport, Success: True, Warning: False, Continue: False, Message:
[8416] 140114.090700.5420: AdminTME: Committer: Completed called
[8416] 140114.090700.5420: AdminTME: Committer: Task was cancelled.
[8416] 140114.090700.5420: AdminTME: Committer: Committer Completed.
Now that I have been verified, I can include this screenshot, where you can see that I am expecting 4 computers to be listed in the pop-up window:
Any additional thoughts? In the meantime, I will be doing some searching on the new adminTME lines.

SBS 2008 - SBS Console and AD errors after migration to new hardware

Hi there,
I'm trying to work out how to fix some of the errors and random behaviour I'm experiencing with the SBS 2008 console and AD related matters since I had to quickly migrate SBS 2008 to new hardware using Windows Server Backup after a failure of the old server.
In my haste to get our email and ftp services back up and running (which use Smartermail and Filezilla respectively instead of Exchange etc) I overlooked the fact that the new server had 3 NICs installed and not one and so restored SBS 2008 and loaded up new
drivers for those and other hardware that had changed (such as the graphics card and mobo. I have since removed the two additional NICs by disabling them on the mobo).
Whilst I got the server up and running again with email and ftp services, even though I currently don't use any AD related stuff directly I have since noted that if I try to say view a list of users that I had previously created via the SBS console, more often
than not it will show no users, and then randomly it will (but when you do see them you can't edit or delete them. I'm aware that I have probably broken a number of golden rules in doing this 'migration' but having a metaphorical gun to my head meant that
I rushed things out of desperation.
Common errors that I experience generally will say things like 'Current security connect is not associated with an Active Directory domain or forest' if I try to list users, or DC not found for domain "xyz.local' etc. I have been searching the net and
trying out some things to fix this but I'm like a dog chasing its tail as I'm not so clued up on server related issues as I am with workstation problems, so if anyone could at least point me in the right direction I would be very grateful. If you require any
info from me (eg diag logs etc) I will be happy to provide them!
Regards,
Dave

Hi Dave,
Based on current situation, please run SBS BPA and fix all that it can find, then monitor the result. For more details, please refer to the following KB.
Windows SBS Best Practices Analyzer (BPA)
Meanwhile, please refer to the following article and repair SBS console.
Repair the Windows SBS 2008 Console
By the way, I noticed that you had got some error messages (such as: “DC not found for domain” and so on). Would you please let me know complete error messages? In addition, when you migrate SBS 2008 to the new hardware, had you done any preparation for
that Source Server? For more details, please refer to the following article.
Migrate Windows Small Business Server 2008 to New Hardware
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

SBS 2008 & Forefront Exchange 2010

Uninstalled the Forefront for Exchange that ships with SBS 2008 and installed the new Forefront 2010 for Exchange. Everything works great but I have a problem with the SBS Console alert. In Forefront Exchange 2010, the Forefront engine takes over the anti-SPAM function from Exchange and that is a good thing, but now the inherent SBS 2008 console has an error message under SECURITY for "Spam protection for E-Mail" as CRITICAL. I know what the problem is but I do not know how to disable the alert. Now that Excahnge is no longer handling anti-SPAM, the SBS server sees the function inactive and issues an alert sice it is unaware that that role is now filled by the Forefront 2010 anti-spam engine. Is there a method do disable the SBS Consoel alert on the SECURITY tab? Everything is working great with Forefront Exchange 2010 on SBS 2008 other than this little alert that is bugging me.
Thanks to anyone out there that has any insight on this...

GaryD9, on this thread:
http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/67eea70a-5ed8-49ae-ba06-6abb2673f38e
posted a detailed answer which worked for me, as far as the Console alert goes. It doesn't fix the emailed reports. I'll copy it here incase that thread becomes unavailable:
the CAUSE of the error is that the MS Exchange "content filter" is turned off in favor of the forefront content filter when forefront is installed. The SBS console is still looking at the Exchange filter status (which is now off) and is generating an
error. On my SBS 2011 server, the cause of this is a file named "E12AntiSpam.xml" in the "C:\Program Files\Windows Small Business Server\Data\SHExtensions" directory. Within that file, there is probably a line such as
$(Get-TransportAgent "Content Filter Agent").Enabled
The fix can be as simple as changing the line to:
$(Get-TransportAgent "FSE Content Filter Agent").Enabled
(just inserting "FSE " in the front of the agent name)
It should be noted that you can't edit this file unless you open it from Notepad after right clicking
on the shortcut for Notepad and selecting "Run as Administrator". Also, you won't see any changes until you close and re-open the Windows SBS Console.
I'm a little concerned that removing the FSE.XML file (as proposed on the SBS forum) may stop ALL error
reporting rather than just changing the source from the regular content filter to the Forefront version. This solution of editing the E12AntiSpam.XML file seems a safer bet.

Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

I'm trying to remove Exchange 2007 from an SBS 2008 server
(Server 2008 Standard FE). My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers. We have two full blown DC's in the environment.
I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server. I can NOT seem to find a TechNet article that shows me how
to proceed in this kind of scenario. I am trying to use the TechNet article:
http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard.
When I go to Disable Mailboxes I get the following error:
Microsoft Exchange Error
Action 'Disable' could not be performed on object 'Username (edited)'.
Username (edited)
Failed
Error:
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
OK
I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010. I just want
to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
Can someone point me in the right direction?
Thanks!

Hi,
Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
On current situation, please refer to following articles and check if can help you.
Transition
from Small Business Server to Standard Windows Server
Removing SBS 2008 –
Step 1: Exchange 2007
Removing SBS 2008 – Step 2:
ADCS
Removing
SBS 2008 – Step 3: remove from domain / DCPROMO
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Hope this helps.
Best regards,
Justin Gu

EBS 2008 Console and SCE 2007 Crashes

Hello,
We recently had an issue where the EBS (Essential Business Server) 2008 Console started crashing. We were able to identify that the OperationsManager database was exceeding the SQL Server Express 2005 DB limit. We referenced the article How
to Maintain and Reduce the Amount of Data Stored in the Systems Center Essentials Databases
http://blogs.technet.com/b/essentialbusinessserver/archive/2010/05/03/how-to-maintain-and-reduce-the-amount-of-data-stored-in-the-systems-center-essentials-databases.aspx
We also found that database size did not decrease and used scripts to reduce the LocalizedText database as it was very large. Since the cleanup we continue to have Event Logs referring to failed inserts and also problems with the RunAs account. All
of the KB articles refer to solutions that require changes in the SCE Console, but the SCE 2007 Console crashes after attempting to run on our EBS 2008 Management server.
How can we resolve our issues if we cannot start the console?

Hi,
Have you checked if event CLR20r3 in the application log? If so, would you please provide detailed information about the error? In addition, have you uninstalled WSUS before? If so, I suspect
it’s because Windows Server Update Service was uninstalled. I suggest we could do a replacement mode install of Management Server. Please perform the following steps to see if it works.
1. Install the management server using the EBS management disk
2. Begin the installation of the EBS Management server and stop once you reach the EBS setup (OOBE) wizard.
3. Press Shift+F10 to open a command shell. From here, install the EBS Preparation and Planning tools, but *DO NOT launch them* after they are installed.
4. Replace WsusSetup.exe with the SP2 version using the following steps.
5. Download the WSUS 3 SP2 x64 version. You can get it here.
6. Rename the downloaded package from WSUS30-KB972455-x64.exe to WSUSSetup.exe
7. Rename C:\Program Files\Windows Essential Business Server\Bin\SCE\Setup\AMD64\WSUSSetup.exe to C:\Program Files\Windows Essential Business Server\Bin\SCE\Setup\AMD64\WSUSSetup.old
8. Copy the new WSUS package to C:\Program Files\Windows Essential Business Server\Bin\SCE\Setup\AMD64\
9. Replace the WSUS_HOTFIX with an update for the Preparation and Planning wizard using the following steps.
10. Rename C:\Program Files\Windows Essential Business Server\bin\WSUS_HOTFIX\KB954960_x64.msp to KB954960_x64.old.
11. Download the KB 977195 update for the Preparation and Planning wizard to the server. Shortcut here.
12. Extract the MSP from the CAB and rename it to KB954960_x64.msp. Copy this KB954960_x64.msp file into the folder C:\Program Files\Windows Essential Business Server\bin\WSUS_HOTFIX\ .
13. Close the command shell and continue with the EBS Management setup. Select NO to updates.
Hope this helps.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Can two servers running windows sbs 2008 be on the same network

I have two HP proliant dl360 servers. We are trying to set up one as a file server. Can we install a copy of Windows sbs 2008 on both machines (we have the license) in the same network

Hi
Every one is quite right you can not install SBS2008 on both machines. Only 1 server on a network can have SBS on it.
However all you need for the second file only server is Server 2008 (it doesn't need to be SBS)
Things to investigate
1. If you have a license for SBS2008 you may run Server 2008 on other servers with no additional client licenses (if you install server 2008R2 or higher on a second or more servers, you will need both SBS2008 and Server 2008R2 client licenses for each user)
So client licenses are sorted
2. If you already have 2 copies of SBS2008 for install, you may find you can downgrade SBS2008 to server 2008 (you will need to double check this, but generally means you can install Server 2008 without having to spend the extra money as you already have
paid for the SBS2008)
3. You may find a old retail copy of Server 2008 on ebay you can buy
Generally the solution to this is, SBS2008 goes on the most powerful server, and is set up as the domain controller, exchange etc.... then on the second server you just install Server 2008 and join it to the domain to be controlled by SBS2008 server, you
don't need to worry about extra CALS, as long as you stay Server 2008 or under
You then set up this second server independently with backups, shadowcopies and shared folders
Group policies for both are configured on the SBS box so you can set up predefined mapping etc
The difficulty you will have is obtaining the old software
If you uses SBS2011 you can use Server 2008R2 and before with no additional CALS
CALS relate to the core OS used, in SBS2008 it is 2008 in SBS 2011 it is 2008R2
Hope this helps
Tris

Excessive hard drive activity on SBS 2008

Hello again. Now that I've essentially solved the network activity problem, I've found that my SBS 2008 server spends a lot of time on hard disk requests that don't appear to have anything to do with it's role as a file server. It's reading between
1-2GB/min. about 50% of the time.
Resource Monitor shows that is from sqlservr.exe. We don't use SQL server or at least not that I'm aware of. It's just a file server now after our Exchange server was moved to the cloud (Office 365) a couple years ago.
I will try attaching a screen cap from Resource Monitor, showing the problem.
Any suggestions on how to solve this problem are welcome.
Thank you,
Mike

Hi Falcon_73,
Please refer to Jason’s suggestion and check if help you to find which sql service caused this issue.
Just addition, did you check the SBSMONITORING database? Please refer to following thread and KB, then check
if can help you.
Solved:
Why is SBSMONITORING Slow/Using all my processor resources?
The Windows SBS Console of Windows Small Business Server 2008
may crash, display "Not Available" for Other Alerts, or require a long time to display the Security and Other Alerts statuses
If anything I misunderstand or any update, please don’t hesitate to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Is it possible to manually setup a Folder Redirection Policy on SBS 2008 for one user? Also are you able to set up folder redirection on a different server than you have SBS 2008 on?

I have a SBS 2008 DC I would like to be able to change the Folder Redirection to a different server. I also would like to be able to test with one user. I read on the forums that it is best to use the wizards for SBS2008. The only problem
I have with using the wizards is that I am unable to test and I am also unable to use a network share for my redirection location.

Hi,
I am sure you would get some help from :
http://blogs.technet.com/b/sbs/archive/2010/10/08/folder-redirection-in-small-business-server-2008.aspx
https://social.technet.microsoft.com/Forums/en-US/448583ca-471e-4a0c-9d26-aa9181e73962/folder-redirection-changing-location?forum=smallbusinessserver
User setting can be found:
Windows SBS Console > Shared Folders and Web Sites > Shared Folders - in Tasks panel click on Redirect folders for user accounts to the server.
Under Folder Names Select folder(s) you want to redirect (e.g. Documents).
Under User Accounts select accounts you want to have folders redirected.
Click OK
Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Revoked Certificate on Outlook 2010/Exchange 2007/SBS 2008

Hi All,
I have an issue that has been frustrating me for quite some time now.
Our setup is SBS 2008 with Exchange 2007. 2 Weeks ago we had to renew our certificate for remote.xxxxxxx.com. This was done through the SBS consoles > Network > Fix my Network and followed the wizard. and this worked fine.
I have however got one user who has a problem and he informs me that this is been an issue since before the cert was renewed.
He is a remote laptop user who visits the office maybe 5 times a month. When launching Outlook 2010 on his machine (Win 7 x64) it comes up with the error: Security Alert, Information you exchange with this site cannot be viewed or changed by others. However,
there is a problem with the Site's security certificate. (Red X) The security certificate for this site has been revoked. This site should not be trusted. Then OK and View Certificate buttons.
I have tried to use the View Certificate to install the certificate to the correct store but no luck. Also tried exporting the cert from the server and installing manually into Trusted Root CA, via MMC Certificates Snap-In and no luck.
I'd like to mention that If i log into a different user, on the same domain, on the same laptop, the issue is gone. So it's local to his profile on the laptop.
Plus, he cannot access the OWA on his laptop either, but again a different user - same laptop can. I have verified that the OWA is still working from another machine in the business, that is using the same certificate. I cannot understand why the
subject machine thinks the certificate has been revoked when I don't believe it has.
Can anybody please shed some light on this situation for me - any avenues to explore would be hugely appreciated.
Many thanks
Nicky

I hope this helps
http://www.msexchange.org/articles-tutorials/exchange-server-2007/management-administration/managing-exchange-certificates-part2.html
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Onsite Scanner Unable To Send Documents Through Exchange 2007 Server (SBS 2008)

I have an SBS 2008 server complete with Exchange 2007 in house and have configured Exchange 2007 to use the Exchange Online Protection (EOP) to process mail for malware, etc. This setup has worked great for the last year or so with no issues.
However, all of a sudden in the last couple of weeks our onsite copier can no longer send documents through email to anyone within the organization. The copier is a Kyocera TaskAlfa 3050CI and exists with the same network. The copier can scan
to a network folder without issue.
If I change the SMTP settings to use a gmail account instead of a local account I can send mail to outside email address. Even with this changed though I still can't send to our domain addresses.
I tried running a message trace from the Exchange Management Console but it doesn't find anything for hte given subject or date/time when I scanned the document.
I am not exactly sure what I should be checking or what piece of the puzzle is causing the problem here. Any ideas on what might be happening or how to correct it?
Thanks so much!

Hi,
Any update? Would you please let us confirm some questions as Howtodo mentioned. Please feel free to let us
know.
Based on your description, it seems that only the copier can’t send documents via emails. On your SBS 2008
environment, please check if some user accounts encounter the similar issue. In other words, did users also can’t send emails attached with documents? If the email was attached with a small size document, will the same result?
In addition, can find any relevant error or events?
Hope this helps.
Best regards,
Justin Gu

Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
failure. I have always felt nervous with SBS because it only runs on a single server.
My plan is:
Install Windows Server 2012 Standard on a new server machine
Join that new server to the existing SBS domain and sync the users, etc.
Install Exchange Server 2013 on the new 2012 Server
Migrate the existing Exchange data and account info to the new server
Demote the SBS Server and promote the new server to primary DC
Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
services)
Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
Thanks,
Colin
Colin

Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
Constraints/objectives:
None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
maintenance.
Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
want to keep all IT tasks as simple as possible.
We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
New Plan:
Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
(or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
it there. In any case, do NOT install Exchange directly on either DC.
Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
Thanks so much for all your help,
Colin

SBS 2008 Console crashing on Network tab

Similar Messages

Maybe you are looking for