SBS 2008 Licensing

I will be migrating from SBS 2008 to Windows 2012 Standard R2 and Exchange 2013 on new equipment. 
Once I have completed the migration and decommissioned the SBS 2008 server, would the SBS 2008 license cover the installation of Windows Server 2008 on the former SBS server?
Thanks in advance.
CC

It wouldn't matter. The premium edition in 2008 and the premium add-on in 2011 are both tied to the existence of SBS on the domain. If SBS is retired then you cannot use the second windows licenses *or* the SQL licenses included as part of the premium offerings.

Similar Messages

  • SBS 2008 - Server Infrastructure Licensing - event id 4 and 38

    Hi everybody,
     I have these errors in Event Viewer
     The Additional Server Count Check in the Licensing component did not pass because error 0x8007200a occurred in function f1031 [WLTT].   The specified directory service attribute or value does not exist.
    Make sure that your DNS server can be contacted and the following services are running: Active Directory Domain Services (NTDS), DNS Server (DNS), Kerberos Key Distribution Center (KDC). This server will be automatically shut down if the issue is not corrected
    FOLLOWED BY
    The Additional Server Count Check detected a condition in your environment that is out of compliance with the licensing policy. This server will be automatically shut down if the issue is not corrected in 58 day(s) 16 hour(s) 30 minute(s). Please look for additional
    events for Additional Server Count Check to troubleshoot.
    BEFORE these events we have 3 informational events:
    Domain Controller Check passed.
    Forest Trust Check passed.
    FSMO Role Check passed.
    We have just ONE server (the SBS 2008, not R2); we had two but the second one (Win2008 Srv) has been dismissed. No reference to the old server is found in AD, registry or other location (DNS, DHCP...). No event about the old server is recorded at all.
    This server is also a DNS server; in its network properties it has itself as the DNS server (I mean: its IP, of course)
    We have no problem in FMSO roles (checked with  "dcdiag /test:fsmocheck")  and the server is going on regularly (no issues with services, users, ...)
    Any idea? I tried to solve this all by myself but with no result at all
    Thanks
    Cosimo
    Milan, Italy

    Hi Justin,
     thanks for your reply. This server was a clean install, but the domain existed before (with a SBS 2003).
    I have a failed test with dcdiag /e /v
            Starting test: NCSecDesc
             * Security Permissions check for all NC's on DC SERVERNAME.
             The forest is not ready for RODC. Will skip checking ERODC ACEs.
             * Security Permissions Check for
               DC=ForestDnsZones,DC=DOMAINNAME,DC=msft
                (NDNC,Version 3)
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have 
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=ForestDnsZones,DC=DOMAINNAME,DC=msft
             * Security Permissions Check for
               DC=DomainDnsZones,DC=DOMAINNAME,DC=msft
                (NDNC,Version 3)
             Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have 
                Replicating Directory Changes In Filtered Set
             access rights for the naming context:
             DC=DomainDnsZones,DC=DOMAINNAME,DC=msft
             * Security Permissions Check for
               CN=Schema,CN=Configuration,DC=DOMAINNAME,DC=msft
                (Schema,Version 3)
             * Security Permissions Check for
               CN=Configuration,DC=DOMAINNAME,DC=msft
                (Configuration,Version 3)
             * Security Permissions Check for
               DC=DOMAINNAME,DC=msft
                (Domain,Version 3)
             ......................... SERVERNAME failed test NCSecDesc
    And BSA shows:
    The DNS client is not configured to point only to the internal IP address of the server. For information about how to fix network settings, see "Managing Your Windows Small Business Server 2008 network" at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=115881).
    +
    There are no DNS name server (NS) resource records with SERVERNAME.DOMAINNAME.msft for the _msdcs delegation in the forward lookup zone astra.msft.
    +
    The DNS CNAME resource record for Connect in the forward lookup zone for Windows SBS 2008 does not exist.
    What would you suggest to me?
    thanks
    Cosimo

  • Migrate SBS 2008 to new hardware

    We have an SBS 2008 installation and are testing a disaster recovery solution by re-installing in Migration Mode.
    Step 5 in the migration document from Microsoft discusses;
        Demote and remove the Source Server from the network
    We'd like to fully test this and get the backup box up and running before signing it off as a working solution.
    Our concern is that, even if we isolate the test machine on a difference subnet from our production LAN, there is some kind of licensing consequence for our running box - via some kind of de-activation signal sent over the net, perhaps - should we continue
    through the final steps.
    Can anyone confirm or deny whether any kind of de-activation occurs? Perhaps paranoia, but thought best to check since we really can't have our live systems shut down.

    Hi,
    Before going further, would you please provide more detailed information about your concern? It’s difficult to understand your needs for me with the information you mentioned. For details about
    how to migrate SBS 2008 to new hardware, please refer to the following articles.
    Migrate Windows Small Business Server 2008 to New Hardware
    http://technet.microsoft.com/en-us/library/cc664208(v=ws.10).aspx
    Moving SBS to new hardware
    http://msmvps.com/blogs/kwsupport/archive/2005/06/18/53958.aspx
    Hope it 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

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

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

  • How can I edit the way autodiscover.xml behaves in SBS 2008 and 2011?

    I have autodiscover working correctly on a few SBS 2008 and SBS 2011 servers. But, its doing its usual misbehaving. When setting up a new Outlook profile, the user enters their email address and password.  Autodiscover is successful in creating all
    the account settings, but at the end of the wizard a username and password window pops up with the users full email address incorrectly filled in as the username, which is why it didn't work.
    This has always been so annoying about SBS.  The user then has to be told to delete their email address in the username field, then fill in "domain\username" instead.  Only then is the authentication successful.
    I've read lots about people adding the external domain UPN Suffix to ADD&T, then manually changing ever users login to domain.com instead of domain.local.   Then you have to mess with the owa authentication settings in exchange to accept the
    UPN.   Its all too ridiculous.  There must be a simpler way.
    I have read about how you can control how the autodiscover.xml behaves, and there are examples of how to do it in this document:
    https://docs.google.com/viewer?a=v&q=cache:0jap1FNKgV0J:https://support.quest.com/Shared/Images/SOL51188_Outlook%2520Automatic%2520Account%2520Configuration.doc+&hl=pl&gl=pl&pid=bl&srcid=ADGEESjizUeFf-JYaM7ZdfIgUCKMMXtcCl0Y3pknFbuwd64GNHIEP1K8a_mpg2YIEisP6sz5DzbtVtdW4Pc42PE0Kjd6bz-3vXz0iaQm7FKi0AnwgvFG_41ZAkBLWynaJtf8s8xyi_d2&sig=AHIEtbSie1mEHTn8el4DPquNxrpovwknUQ
    The document above shows the settings we need to change.  It looks like we can add the local domain using DomainName into the autodiscover.xml and this will stop autodiscover reporting that the full email address is required.  So we
    should be able to get autodiscover to populate the username pop-up with with "domain\user" automatically. 
    OK, so my question is, how on earth do I edit these settings in SBS 2011?  I can't find any articles that talk about how to edit autodiscover. 
    If I could just edit this one setting (that Microsoft should have correctly configured in the first place) autodiscover will work perfectly for all existing users and all future users, without having to do anything.

    Just to straighten out a few things;
    1) This is NOT a bug, rather by design. Not every active directory has an exchange server in place, and MS is assuming you don't want to give your internal domain name out to people (which is why it doesn't default to domain\username)
    2) Going on what I said in 1), this is NOT SBS specific this is the same way with every Active Directory/Exchange install, keep in mind Microsoft did NOT specially design the software for SBS, they just bundled it into a supported configuration in a neat
    little package -since the Exchange server we run on SBS is the same Exchange server powering hundreds of hosted email providers -it makes sense why autodiscover doesn't provide the domain\username (imagine what a mess that would be!)
    3) I understand it's a little bit time consuming but it can actually be done for all users in a matter of seconds, select all users, right click and go to Properties, you can then choose the UPN Suffix for all users. When a new user gets created one of the
    settings in the wizard is the UPN suffix and is easily changeable as long as you notate for the person creating the user to do it. (The problem here is if you're using the SBS Console instead of AD to setup the User in which case that's just an oversight
    in design not a bug in the programming)
    4) You can most certainly have a powershell script that changes the UPN suffix from A to B, let me know if you're interested I'll dig one up for you. That can be run on a scheduled task and will solve the remaining issues you have :)
    I do see you mentioned it in number 3, I must have missed since I didn't re-read the OP before posting the article, however I just tested on several SBS 2011 machines and OWA authentication settings don't have to be changed at all, this worked immediately
    for Outlook Anywhere and Outlook Web Access in my lab and two different customer production systems.
    -GreenlightTech

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

  • Issues After Disabling IPv6 on Your NIC on SBS 2008

    If you uncheck the IPv6 protocol from your network interface card on your Windows SBS 2008 server you may see the following issues after a reboot:
    Microsoft Exchange services fail to start
    Server hangs at “Applying Computer Settings…” (can eventually logon after 30 – 60 minutes)
    Network icons show as offline
    Some or all of the following events
    Application Log Events
    Source: MSExchange ADAccess
    Event ID: 2114
    Task Category: Topology
    Level: Error
    Description:
    Process MAD.EXE (PID=2088). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185,
    “Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
    Source: MSExchange ADAccess
    Event ID: 2601
    Task Category: General
    Level: Warning
    Description:
    Process MSEXCHANGEADTOPOLOGY (PID=952). When initializing a remote procedure call (RPC) to the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the SID for account <WKGUID=DC1301662F547445B9C490A52961F8FC,CN=Microsoft Exchange,CN=Services,CN=Configuration,…>
    – Error code=80040a01.
    The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
    Source: MSExchange ADAccess
    Event ID: 2102
    Task Category: Topology
    Level: Error
    Description:
    Process MAD.EXE (PID=2088). All Domain Controller Servers in use are not responding: SBS.sbs2008.local
    Source: MSExchange ADAccess
    Event ID: 2105
    Task Category: Topology
    Level: Warning
    Description:
    Process MAD.EXE (PID=2088). Exchange Active Directory Provider failed to obtain DNS records for domain sbs2008.local. DNS Priority and Weight for the Domain Controllers in this domain will be set to the default values 0 (priority) and 100 (weight).
    Source: MSExchange ADAccess
    Event ID: 2114
    Task Category: Topology
    Level: Error
    Description:
    Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=952). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge
    Base article 218185, “Microsoft LDAP Error Codes.” Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.
    Source: MSExchangeFBPublish
    Event ID: 8197
    Task Category: General
    Level: Error
    Description:
    Error initializing session for virtual machine SBS. The error number is 0x80040a01. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.
    Source: MSExchangeTransportLogSearch
    Event ID: 7005
    Task Category: General
    Level: Error
    Description:
    Microsoft Exchange couldn’t read the configuration from the Active Directory directory service because of error: Failed to load config due to exception: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException: The Exchange Topology service on server
    localhost did not return a suitable domain controller.
    System Log Events
    Source: Service Control Manager
    Event ID: 7044
    Task Category: None
    Level: Warning
    Description:
    The following service is taking more than 16 minutes to start and may have stopped responding: Microsoft Exchange System Attendant
    Source: Service Control Manager
    Event ID: 7022
    Task Category: None
    Level: Error
    Description:
    The Microsoft Exchange Transport service hung on starting.
    Source: Service Control Manager
    Event ID: 7024
    Task Category: None
    Level: Error
    Description:
    The Microsoft Exchange Information Store service terminated with service-specific error 0 (0×0).

    Hi,
    Based on your description, it seems to be the same as the following blog.
    Issues
    After Disabling IPv6 on Your NIC on SBS 2008
    Did you mean that encounter the same issue? If so, there is a resolution in that blog, please check if can
    help you solve the issue.
    If any other issue exists or any update, please don’t hesitate to let me know and provide more details. It
    will help me understand clearly.
    Best regards,
    Justin Gu

  • 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

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

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

  • Migration from exchange SBS 2008 to Microsoft exchange 20013

    i have started an upgrade of an SBS 2008 to an exchange 2013 
    i installed the 2 server in coexistence and moved all mailboxes as well as all public folders 
    what should i do next to be able to decommission the SBS and turn it off completely
    PS: our company does use third party certificate as all the users are local users on TS server
    much appreciate it 

    Please follow the Microsoft Exchange Server Deployment Assistant
    which is web-based tool that asks you a few questions about your current environment and then generates a custom step-by-step checklist that will help you deploy different versions of Exchange Server for different types of scenarios.
    http://technet.microsoft.com/en-in/exchange/jj657516.aspx
    Exchange Queries

  • 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 - 'Sites' Certificate Expired - How to find out where/service it's used - if at all

    Greetings,
    Is there a way to see what options or services might be using the default sites certificate on our sbs 2008 server?
    PowerShell or Certificates MMC add-in?
    We have a Go Daddy for email and remote - so I'm thinking this self-signed- expired certificate can be deleted.
    Thank you
    Thanks in advance

    Hi,
    As far as I know, we could only use Certificates console check the certificates for the logged on user, for the specific service account and for the specific computer account. It’s hard to
    verify which option needs a specific certificate.
    For details about Certificates Console, please refer to the following article.
    Certificates Console
    http://technet.microsoft.com/en-us/library/cc962086.aspx
    Best Regards,
    Andy Qi
    TechNet Subscriber Support
    If you are
    TechNet Subscription user and have any feedback on our support quality, please send your feedback
    here.
    Andy Qi
    TechNet Community Support

Maybe you are looking for