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.

Similar Messages

  • 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

  • User log in bogging down network - How to QOS / Bandwidth per computer

    Hi,
    I am working with a slow network (100mbs), we are having an issue were one user has a large profile and when that user logs in onto a new computer it almost halts the network.
    The obvious solution it to install a 1GB switch, which I am going to do but...
    This company is rapidly growing and it wont be long before there are several users with large profiles logging in simultaneously. 
    I would like to implement some sort of QoS policy where each computers connection to the server is limited to a max of say 100mb.
    Can this be done with built in GPO's or Free Software.
    The site is running a single server 2012 domain controller. that is also the file server.
    Thanks in advanced for any help you can give.
    Cheers

    Hi,
    >>Can this be done with built in GPO's or Free Software
    Before going further, we can use GPO to configure policy-based QoS to manage network traffic.
    Regarding this point, the following articles can be referred to as reference.
    Policy-based Quality of Service (QoS)
    https://technet.microsoft.com/en-us/library/jj159288.aspx
    Configuring Policy-based Quality of Service (QoS)
    https://technet.microsoft.com/en-us/library/hh831689.aspx
    >>The obvious solution it to install a 1GB switch, which I am going to do but...
    Based on the description, I do agree that this should be the way to go.
    Best regards,
    Frank Shen
    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 Subscriber Support, contact [email protected]

  • 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

  • Error 0xE0000235 when trying to download a driver onto Windows SBS 2008 64-bit Standard FE.

    Unfortunately, Error 0xE0000235 occurs when trying to download a driver onto Windows SBS 2008 64-bit Standard FE.
    I am installing the GV 800 GeoVision 32/64Bit 16CH Video Capture Card onto the server.
    Please urgently assist.
    Answer in clear English. Cryptic answers not welcome. Yes...I know you are an intelligent, highly valuable expert on the world's leading edge technology.

    Hi, I'd like to inform you that the error code 0xE0000235 refers to "Error in WOW64". This can be caused by corrupted or incompatible driver of the Video Capture Card. Similar issue may also occur on other driver on other operating system and I don't think
    this can be caused by SBS2008 blocking the driver.
    I suggest you contact with GeoVision Technical Support (http://www.geovision.com.tw/english/4_0.asp) and see if their driver should work on SBS2008 and make sure that you have downloaded
    latest driver from their site:
    http://www.geovision.com.tw/english/5_2.asp
    Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    Hope this helps!
    Sean Zhu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact
    [email protected]
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • 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]

  • Connecting remotely to SBS 2008

    I've been reading a great many posts concerning similar issues, but none of them, nor responses quite fit the bill.
    I'm running SBS 2008 with Remote Web Workplace enabled, etc. All Windows Client computers are able to access the server and networked machines perfectly well from outside the domain. Also, a VPN can be established via a Windows machine to the server and resources can be used remotely, as designed.
    My Mac, running Leopard, can access the server using a vpn; that is, it gives me a "connected" message when I supply correct credentials and the IP of the internet domain name of the server. However, I am unable to access any network resources, nor can I use the Remote Desktop Connection for Mac provided by Microsoft.
    The Remote Desktop app will attempt to connect but will issue a prompt to me that the connection was ended at the server end, or it will claim address does not exist. These are local domain addresses, as I am supposedly linked to the domain via VPN, but I'm making that up . . . However, if I am not linked to the vpn and utilize the internet domain name, the same thing occurs.
    If I am connected to the vpn, I cannot access any network resources using the "connect to server/folder" procedure described in the literature. "Folder cannot be found" is the consequence of above.
    Of interest, the Remote Web Workplace can be accessed using Safari and server address above, but, of course, one cannot remote connect to any computer on the network because of lack of ActiveX stuff.
    Any ideas out there?

    The solution to above problem lay in the certificate. What the error messages were trying to tell me was the certificate was not "pointing" to the correct location: ie, the internet domain name of the local resource had to be added to the certificate as a new preference. SBS 2008 will disconnect any user without a certificate specifically from the server, and the Keychain needed be directed to supply the correct cert when required.
    So the process: download certificate from Server/Downloads; drop into Keychain and change trust settings to "trust"; go to File/New Certificate Preferences and select above certificate and enter correct internet domain name for server; go to System Preferences/Network and add a VPN connection (PPP); enter correct user account and authentication password for server; in ADVANCED, enter correct address for DNS server (usually same as server IP) and Search Domain (the internal domain name of server); connect to VPN, and once connected, go to top menu (Finder) and select Go/Connect to Server and enter smb://server name

  • Server 2012 std not able to see Domain, DC and DNS on Win SBS 2008 std Domain

    Hi There
    I have a HP ML 110 G5 SBS 2008 std server as my DC on my network. I recently added a HP Microserver running Server 2012 std (with no roles or features installed) to act solely as a file server for a 3rd party program as the program was not running efficiently
    on the main server.
    The problem I am having now is that the 2012 server keeps falling off the domain and cannot contact DNS server. I have also had to re-enable remote desktop several times. It also shows the 2012 Server as being on a private firewall profile and not on the
    domain firewall profile but I suspect that this is part of the same problem. 
    the resulting problem that this is causing is that the local machines that need to contact an SQL database on the 2012 fileserver intermittently either time out or are very slow to connect.  
    So far I have tried: 
    Switching from Static IP to DHCP. 
    Re-adding the server to the domain. 
    Stopping and restarting DNS services on the DC.
    Checking physical Network connections and routing.
    Putting the 2012 server into the same Organizational Unit as the 2008 DC. 
    Has anyone else encountered this problem when adding a 2012 server to a 2008 domain?  I have a feeling that the solution is probably something simple that I've overlooked, but I can't think what.  Any help would be greatly appreciated. 
    Regards
    Russ
    Also, as some additional info -
    Event viewer gives the following errors:
    Group Policy Error:
    Log Name:      System
    Source:        Microsoft-Windows-GroupPolicy
    Date:          2015-04-27 01:17:51 PM
    Event ID:      1129
    Task Category: None
    Level:         Error
    Keywords:      
    User:          SYSTEM
    Computer:      [SERVERNAME].[DOMAIN].local
    Description:
    The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has
    successfully processed. If you do not see a success message for several hours, then contact your administrator.
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-GroupPolicy" Guid="{AEA1B4FA-97D1-45F2-A64C-4D69FFFD92C9}" />
    <EventID>1129</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-27T11:17:51.111942100Z" />
    <EventRecordID>19056</EventRecordID>
    <Correlation ActivityID="{C0CBAF2B-1E93-49C0-B910-069AE43F74B2}" />
    <Execution ProcessID="732" ThreadID="1336" />
    <Channel>System</Channel>
    <Computer>[SERVERNAME].[DOMAIN].local</Computer>
    <Security UserID="S-1-5-18" />
    </System>
    <EventData>
    <Data Name="SupportInfo1">1</Data>
    <Data Name="SupportInfo2">1548</Data>
    <Data Name="ProcessingMode">0</Data>
    <Data Name="ProcessingTimeInMilliseconds">0</Data>
    <Data Name="ErrorCode">1222</Data>
    <Data Name="ErrorDescription">The network is not present or not started. </Data>
    </EventData>
    </Event>
    DNS Error:
    Log Name:      System
    Source:        Microsoft-Windows-DNS-Client
    Date:          2015-04-27 04:54:58 PM
    Event ID:      8015
    Task Category: (1028)
    Level:         Warning
    Keywords:      
    User:          NETWORK SERVICE
    Computer:      [SERVERNAME].[DOMAIN].local
    Description:
    The system failed to register host (A or AAAA) resource records (RRs) for network adapter with settings:
               Adapter Name : {3DDD0E46-D879-48C0-9DF6-5FAC0F1A56C4}
               Host Name : [SERVERNAME]
               Primary Domain Suffix : [DOMAIN].local
               DNS server list :
    192.168.2.10
               Sent update to server : <?>
               IP Address(es) :
                 192.168.2.15
    The reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running
    at this time. You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" />
    <EventID>8015</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>1028</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2015-04-27T14:54:58.599130300Z" />
    <EventRecordID>19105</EventRecordID>
    <Correlation />
    <Execution ProcessID="856" ThreadID="952" />
    <Channel>System</Channel>
    <Computer>[SERVERNAME].[DOMAIN].local</Computer>
    <Security UserID="S-1-5-20" />
    </System>
    <EventData>
    <Data Name="AdapterName">{3DDD0E46-D879-48C0-9DF6-5FAC0F1A56C4}</Data>
    <Data Name="HostName">[SERVERNAME]</Data>
    <Data Name="AdapterSuffixName">[DOMAIN].local</Data>
    <Data Name="DnsServerList"> 192.168.2.10</Data>
    <Data Name="Sent UpdateServer">&lt;?&gt;</Data>
    <Data Name="Ipaddress">192.168.2.15</Data>
    <Data Name="ErrorCode">1460</Data>
    </EventData>
    </Event>

    Can you post an ipconfig /all from the server and the DC?
    Robert Pearman SBS MVP
    itauthority.co.uk |
    Title(Required)
    Facebook |
    Twitter |
    Linked in |
    Google+

  • Problem connecting to MS Exchange 2007 on SBS 2008

    I am having problems connecting to Exchange via cfexchangeconnection. Our ColdFusion environment is CF9 Enterprise on Win 2008, and the Exchange host is Win SBS 2008 (which uses IIS7).
    After having worked through the documentation and following all procedures outlined at
    http://help.adobe.com/en_US/ColdFusion/9.0/Developing/WSc3ff6d0ea77859461172e0811cbec14f31 -7fed.html
    plus googling intensively, we have the following method to test the connection
    <cfexchangeconnection action="open"
             connection="thisExchangeConnection"
             server="portal.mydomain.com"
             protocol="https"       
             formBasedAuthentication="true"
             formBasedAuthenticationURL="https://portal.mydomain.com/owa/auth/owaauth.dll"
             mailboxname="myMailBox"       
             username="myUsername"
             password="myPassword" />
    <cfdump var="#thisExchangeConnection#">
    <cfexchangeconnection action="close"
             connection="thisExchangeConnection" />
    The IIS7 implementation in SBS 2008 is quite a lot different to Win 2008, so there are some question marks around some steps in the above documentation. However, we have made sure that:-
    1) you can use the credentials above to login via a web browser
    2) WebDav is on in IIS
    3) there is no IWA and forms based authentication is on
    4) certificates are installed correctly on both the CF and Exchange servers
    5) the myUsernameaccount has correct permissions in iis/owa/exchange
    Despite this, the net result is always
    Access to the Exchange server denied. 
    Ensure that the user name and password are correct.
    From research it seems that a lot of people have issues where the underlying problem is actually an Exchange 440 timeout error where the password in the IUSR_<servername> and IWAM_<servername> (IIS/Active Directory) is out of sync.
    I was pinning my hopes on the above being the problem but now I find that in SBS 2008 there is no IWAM_<servername> server account.
    All this leads me to ask is SBS 2008 actually compatible with the cfexchange tags in CF9? There is nothing in the documentation that I can find that syays that it isn't, but given the amount of time we've spent on what should be straightforward I am wondering if we are on a hiding to nothing. Anyone from Adobe care to comment?
    If anyone has managed to get this to work specifically with SBS 2008, or has any advice I'd be grateful to here from you.

    Hi,
    As said by Sneff , I would also recommend to enable Logging to get more detailed information. Also follow
    Configuration of POP/IMAP on SBS 2008 Refer to :
    http://blogs.technet.com/b/sbs/archive/2008/09/19/how-to-configure-sbs-2008-to-host-pop3-imap4.aspx
    http://blogs.technet.com/b/sbs/archive/2011/08/31/how-to-configure-outlook-for-pop3-imap-and-smtp-connectivity-in-sbs-2008-2011-standard.aspx
    As per the error code, you need to follow
    http://support.microsoft.com/kb/813514/EN-US
    I would also disable AV on both Client machine and TEST , including the Filters of AV.
    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.

  • Unable to install security updates via WSUS on Windows 2008 client servers

    When I try install to install updates on Windows 2008 client servers I get the error : Code 80244019  Windows Update encountered an unknown error
    After running the WSUS Client Diagnostic Tool I get the result : GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002 The system cannot find the file specified.
    On a Windows 2003 server the WSUS Client Diagnostic Tool shows no error message. So I guess the problem seems to be specificly related to Windows 2008 servers.
    The client server has been integrated into a WSUS console version 3.2.7600.226 runnning on a Windows 2003 Enterprise Edition SP2.
    Thanks in advance for the help in resolving this issue.

    When I try install to install updates on Windows 2008 client servers I get the error : Code 80244019  Windows Update encountered an unknown error
    The 0x80244019 error is an HTTP 404 error and when encountered trying to "install updates", which really occurs when trying to
    download the update files so that the updates can be installed, is almost always a function of the desired file having been manually deleted from the WSUS server. The file that should be there for the needed update, isn't, but it used to be.
    If all of the clients are getting this error on all updates, then that's a function of the content store on the WSUS server being missing, in the wrong place, or configured with the wrong ACLs.
    After running the WSUS Client Diagnostic Tool I get the result : GetFileVersion(szEngineDir,&susVersion) failed with hr=0x80070002
    This result is inconclusive, and not really relevant. The CDT is 32-bit only and can't be used on 64-bit systems. Plus, we already know the client is talking to the WSUS server -- you've reported the error code -- so the Client Diagnostic Tool will
    tell us nothing of use at this point (even if it did work on 64-bit systems).
    On a Windows 2003 server the WSUS Client Diagnostic Tool shows no error message.
    Cool. It works on a 32-bit system.
    So I guess the problem seems to be specificly related to Windows 2008 servers.
    No... BUT... allow me to make an example of this for just a moment, and forgive me for that.
    This is a great example of arriving at the wrong conclusion, caused by not considering ALL of the differences, as well as the scope and capability of the diagnostics performed. The error is not because one is '2003' and the other '2008; the error is because
    one is 'x86' and the other is (obviously) 'x64'. And, in either case, diagnosing the client was wasted effort because the client is already working. (It got a real HTTP error message from the WSUS server.)
    Now, we need to get some real diagnostic information to find out why you're getting this error code. :-)
    Please post the actual entries from the WindowsUpdate.log where this error code appears, plus a hundred lines prior, and let's get some context around the error code, and the exact update that's involved in this issue.
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Macbook pro with OS 10.6.4 cannot join Windows SBS 2008 .local domain

    Hi,
    I just had a windows SBS 2008 installed and it controls a .local domain where all my Windows7 PC's are connected to. I can access the internet wired/wirelessly but i cannot see any of the computers on the network at all, thus i cannot share files or share the printer which is connected to one of the local PC's.
    I have read many threads indicating possible fixes but no one has been able to give me a permanent solution. Is this inability to connect my MAC to the SBS 2008 local domain fixable from my MAC or is it to be resolved from the SBS 2008 side? Any help would be greatly appreciated.

    Greetings,
    Download the combo update (don't install it yet): http://support.apple.com/kb/DL1400
    SafeBoot your computer: http://support.apple.com/kb/HT1455
    While in SafeBoot install the combo update
    Restart the computer to come out of SafeBoot
    Try running software update again and see if it works.
    Hope that helps.

  • WSUS timeout issues on SBS 2008 with WSUS 3.0

    I am having a heck of a time using the Server Cleanup Wizard, keep getting timeouts on the Unused updates and update revisions section.
    After a few hours I get the timeout message and an option to reconnect to the node.
    Here is the message that I copied to the clipboard, which is also in the event viewer as event id 7042:
    The WSUS administration console was unable to connect to the WSUS Server Database.
    Verify that SQL server is running on the WSUS Server. If the problem persists, try restarting SQL.
    System.Data.SqlClient.SqlException -- Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.
    The statement has been terminated.
    Source
    .Net SqlClient Data Provider
    Stack Trace:
       at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
       at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
       at Microsoft.UpdateServices.UI.SnapIn.Wizards.ServerCleanup.ServerCleanupWizard.OnCleanupComplete(Object sender, PerformCleanupCompletedEventArgs e)
    I have tried, I believe, all of Mr. Garvin's excellent advice, like defrag the file system, run the maint. script, and do the options of the cleanup wizard one at a time.  All of the other options worked.
    I have also declined all the superseded updates, checked to make sure only my products were downloaded, and made sure that updates are only in English.
    I followed Mr. Garvin's excellent post at the PatchZone, and tried to read everything he has written about this subject (that was a lot of content!)  At this point I think I am stumped, what else can I try other than a re-install of WSUS, which I don't
    really want to do, but will if that's the only option.  Is that even possible with SBS 2008?
    Thank you all in advance!

    I followed Mr. Garvin's excellent post at the PatchZone, and tried to read everything he has written about this subject (that was a lot of content!). At this point I think I am stumped
    Perhaps you overlooked the singular advice to Keep Running the "Delete unused updates.." until it does NOT timeout?
    This operation is atomic. It does make progress each time you run it. The timeout is a manifestation of ASP.NET getting bored waiting on the SQL Server Stored Proc, NOT a manifestation of anything failing inside the database. Each time you run the task and
    it times out, it DID delete some updates (you just don't get any stats on that because ASP.NET wimped out). When the task finally completes successfully, the SCW UI will show you the results (from the last run).
    Lawrence Garvin, M.S., MCSA, MCITP:EA, MCDBA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2014)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence%20R%20Garvin-32101
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

  • Extend SBS 2008 - 2011 Migration

    Yes, I know the SBS party has passed.  But, I have a client who purchased it before the end of the year, and we are now doing a migration from SBS 2008 to SBS 2011.  However, it is taking longer than 21 days.
    I know with SBS 2003, you can suspend SBCore and extend the migration.
    Can you do the same with SBS 2008?

    Hi,
    Any update?
    Just checking in to see if the suggestions were helpful. Please let us know if you would like further assistance.
    Best Regards,
    Andy Qi
    TechNet
    Subscriber Support
    If you are TechNet
    Subscription user and have any feedback on our support quality, please send your feedbackhere.
    Andy Qi
    TechNet Community Support

  • 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 to Exchange 2013 - "Create legacy Exchange host name"... Single External IP?

    Migrating a customer to Exchange 2013 from SBS 2008.
    Once of the Pre-reqs is to setup an external A record for legacy.customer.com for the external IP address of the old Exchange server.
    The customer only has a single external IP address...
    So what do I do for this external DNS of legacy.customer.com?

    Hi Allister - 
    You shouldn't need an EXTERNAL dns entry for legacy. Here's how it works:
    Client from outside -> External IP to Exchange 2013 (now here's where the interesting thing happens)
    Exchange auto-magically proxies mailboxes on the old environment. Reason being: New Exchange Servers always know how to get to old servers. You just change all the internal URLs to legacy. (or you can even do oldmail., whatever you like) and since this information
    is inside AD, Ex2013 will find it.
    These are the URLs you need to change in 2007/2010
    ClientAccessServer
    webservicesvirtualdirectory
    oabvirtualdirectory
    owavirtualdirectory
    ecpvirtualdirectory
    ActiveSyncVirtualDirectory
    AutodiscoverVirtualDirectory You can read more on how to set these here:
    http://social.technet.microsoft.com/wiki/contents/articles/5163.managing-exchange-2010-externalinternal-url-s-via-powershell.aspx
    Here's the Million dollar question though: being SBS 2008, does this have exchange 2007 or 2010 on it? If it's 2010, you don't need the legacy namespace anymore. 2007, you do. Connect to https://ex2013server/owa and log into a mailbox on the 2010 environment.
    If you can get there (you'll know cause it flipped over to a 2010 interface) then it's working.
    A wise man is a fool, with a good memory.

Maybe you are looking for