Migrating Small Business Server 2008 to Server 2012 R2 Standard

Hi All,
We are going to migrate SBS 2008 to Server 2012 R2 Standard for one of our customer.
We cannot find a  proper guide to do the migration. Any idea for this process.
We already migrated email to Office 365. We are going to migrate Active Directory and Shared data to new Server 2012 R2 Standard.
Thanks,
MKH

Hi,
Thanks for your posting.
There is a similar thread has been discussed:
Migrating from SBS 2008 to Windows Server 2012 R2 (NOT Essentials and with NO Exchange)
http://social.technet.microsoft.com/Forums/en-US/1276d2d3-a8f2-4786-82f3-4308a2affb11/migrating-from-sbs-2008-to-windows-server-2012-r2-not-essentials-and-with-no-exchange?forum=smallbusinessserver
Regards.
Vivian Wang

Similar Messages

  • Is it possible to migrate Small Business Server 2008 to Exchange 2013 install on it's own member server?

    Trying to figure out of migration to Exchange 2013 is possible on a existing SBS 2008 with Exchange 2007.  If it's possible, is it support by Microsoft as well?
    Thank you!

    Are you planning to get rid of the SBS server or you would like to keep it as a DC, DHCP, DNS, and SharePoint server?
    You should be able to upgrade to Exchange 2013, but there are more details to consider. The following six part series outlines this process:
    Migrate from SBS 2008 or 2011 to Standard Edition Products
    Step by Step Screencasts and Video Tutorial

  • Migrate Small Business Server 2003 to Exchange 2010 and Windows 2008 R2

    I am trying to migrate my server SBS 2003 to win server 2008 r2 and exchange 2010.
     I got error message when trying to install exchange 2010 server.
    Error:
       Installing product E:\exchangserver.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is 'Error reading from file E:\Setup\ServerRoles\ClientAccess\owa\bin\DocumentViewing\isgdi32.dll.
    Verify that the file exists and that you can access it.'.
    Fatal error during installation

    Hi Mike,
    Error 1603 "Fatal Error" indicates that issues with Media type or Windows installer file not correctly installed.
    I recommend you check the media you are installing. Change ISO files and reinstall.
    Here are some threads for your reference.
    Error 1603 during a new installation
    http://social.technet.microsoft.com/Forums/exchange/en-US/1de7daab-9cdd-4696-8cc4-6b4418be33ca/error-1603-during-a-new-installation?forum=exchange2010
    Fatal error during installation. Error code is 1603
    http://social.technet.microsoft.com/Forums/exchange/en-US/a325132a-5e3d-4496-adec-4ccdbb0d6c92/fatal-error-during-installation-error-code-is-1603?forum=exchangesvrdeploy
    Hope it helps.
    If there are any problems, please feel free to let me know.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Windows small business 2011 standard cannot be upgraded to windows server 2012 R2 Standard

    Can Sbs 2011 r2 standard upgrade to 2012 r2 standard?

    Hi,
    I agree with Cliff. There is no in-place upgrade and we have to do a migration.
    Regarding how to migrate Small Business Server, the following article can be referred to as reference.
    Windows Small Business Server Migration
    http://technet.microsoft.com/en-us/sbs/gg981878
    Best regards,
    Frank Shen

  • Migration of Windows Small Business Server 2003 to Windows Server 2012 Essentials

    Hi,
    I am trying to migrate Windows Small Business Server 2003 to Windows Server 2012 Essentials by following the steps given in the link below:
    http://technet.microsoft.com/en-us/library/jj200112.aspx
    I have looked at other threads on the forum but none of them have been too helpful.
    The issue: When
    I run the Migration Preparation Tool on the Source Server, it runs successfully and does not report any errors. However, when I try installing Windows Server 2012 Essentials on the Destination Server, it displays an error that says 'Source
    Server not prepared for migration: After you run the Migration Preparation Tool successfully on your source Server, click retry'.
    The Source Server has 2 network adapters-one for the local network and the other for connection to the internet and the router is set as the default gateway this adapter.
    Since it is mentioned in the documentation - 'configure your Source Server to use one network adapter', I'm wondering if this is the issue and I need to make changes in this configuration? 
    On running the Microsoft IT Environment Health Scanner tool it
    reported an error - 'DNS Server listening on multiple addresses' and a warning ‘Domain Controller listening on multiple addresses’. Both point to the same solution KB 272294 (http://support.microsoft.com/kb/272294).
    But it did not remove the errors.
    Other steps performed:
    As per the steps, I performed a backup, installed recent service packs and synchronized the source server time with external source.
    On running the Best Practices Analyser. It shows 3 warnings.
    - The threshold for the Allocated Memory alert is set to the default value. However the server has more than 2 GB of RAM installed.
    - Microsoft Outlook Client not installed" Text="Microsoft Outlook Client is not installed in the ClientApps folder. You must run Windows SBS integrated setup.
    - The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000. The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000.
    I also ran the Ran netdiag.exe, dcdiag.exe commands
    and no failures were reported.
    The Event Viewer does not show any errors.
    Not sure to what extent these warnings would affect the migration. 
    Any help would be appreciated. Thanks!

    The SBS2003 needs to use one NIC only so you'll need to change that before starting. If it is the premium version and has ISA server installed, that will need to be removed first.  See:
    http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx
    -- Al

  • How long does Microsoft Small Business Server 2008 support?

    Hi,
    How long does Microsoft SBS 2008 (Vista like server installation)? At what time we have to upgrade our server?
    Thanks, 
    Eddy

    Hi Eddy,
    Below article take you to support like cycle of SBS 2008.
    http://support2.microsoft.com/lifecycle/?p1=13231
    You will not see exact support date mentioned here as the underlying component is a Windows 2008 server and if you take windows 2008 the extended support is still the year 2020 as per the below Microsoft article.
    http://support2.microsoft.com/lifecycle/?p1=12925
    and life cycle of various Microsoft products can be cross checked at the below reference article:
    http://support2.microsoft.com/gp/lifeselectserv?wa=wsignin1.0
    Upgrade ?
    I suggest you to plan upgrade based on your requirement ? What applications you are using on existing environment and what user need you are expecting ? based on these you need to plan whether you need to migrate to a new platform or not ? Also you need
    to decide which version of Windows you want to migrate ? SBS version ? or Non SBS versions ( I mean other than SBS family).
    You can see more details on Windows Essentials here: http://en.wikipedia.org/wiki/Windows_Server_Essentials
    http://blogs.technet.com/b/sbs/archive/2012/07/05/windows-small-business-server-essentials-becomes-windows-server-2012-essentials.aspx
    Feel free to post for any queries.
    Regards, Prakash Nimmala Skype : Prakash.Nimmala Email ID : [email protected] Whenever you see a helpful reply, click on Vote As Helpful & click on Mark As Answer if a post answers your question. http://prakash-nimmala.blogspot.in/

  • Can i upgrade exchange 2007 to exchange 2013 on same small business server 2008 machine?

    Hi,
    I have small business server 2008 with exchange 2007 installed in my organization,
    Now I need to upgrade exchange 2007 to exchange 2013 on same small business server 2008 standard edition.
    I already tried to upgrade but not successful.
    can i upgrade exchange 2007 to exchange 2013 on same small business server 2008 machine or any alternate through which it is possible.
    Please share any MS article if it not possible. 
    Thank you in advance
    Regards
    arun av

    Hi Arun,
    Its really great that you want to move and upgrade old Exchange to new Exchange server. The manual steps and guide is already recommended to you.
    Moreover, I would like to recommend you to use an automated tool to upgrade your Exchange server 2007 to exchange 2013.  I have tried and test tool to do Exchange Migration 2007 to 2013. You can follow the link 
    http://www.exchange2007to2013migration.exchangemigrationtool.com/. It will also help you to do Intra-Cross forest migration if you required.
    Hopefully my recommendation will surely help you.
    Thanks,
    Walter

  • UDP when adding Server 2012 R2 to a Small Business Server 2003 Domain

    So we have a Small Business Server environment. Migrating to Windows Server 2012 R2 VMs. Currently the entire old SBS environment is still in existence. I've added 2nd 2012 DC, 2012 RDS VM, and a Server 2012 File Server as well that will host the UDPs.
    (Everything is working so far) BUT On the RDS Server I point the UDP Wizard to the share created on the File Server. The UDP does not appear to be created when logging into a desktop collection. The template VHDX is there but nothing else is created in the
    shared folder on the file server.
    I've stumbled upon people having issues with network shares and SMB versions. Do you think this could be an issue with the SMB client, etc since I'm adding them to an older domain? IF so how do I check or upgrade the client version? Will this cause the existing
    SBS 2003 users from seeing this network share or cause any other issues? I really didn't think it would be an issue because the File Server and the RDS Server are both 2012 R2.
    Thanks for any help!

    Hi,
    Thank you for posting in Windows Server Forum.
    Here letting you know to just recheck the configuration. If possible, try to remove the old UPD and collection; create new user under ADUC, Add that user to the same domain as of file server & RDS Server 2012 R2, then create a new share on your file server,
    create new collection, and provide the actual path of the share and after that it will create a template. Once user will login to the client system for 1st time there will be available UPD (vhdx file) for the users.
    For more detailed you can refer following article.
    Easier User Data Management with User Profile Disks in Windows Server 2012
    http://blogs.msdn.com/b/rds/archive/2012/11/13/easier-user-data-management-with-user-profile-disks-in-windows-server-2012.aspx
    Working with User Profile Disks on Session-Based Desktop Deployments
    http://www.virtualizationadmin.com/articles-tutorials/vdi-articles/general/working-with-user-profile-disks-on-session-based-desktop-deployments.html
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • About SQL 2008 on any Windows Small Business Server

    Hi, I try to install only 1 Server, we need that server run all setting (manage) of domain controller, active directory and sql. Please let me know if its possible install SQL 2008 (What ever versión) on Windows Small Business Server what
    ever year (2012, 2008, Etc.) without having problems with the domain controller, firewall, sharing the SQL to network computer and the Windows Server year and versión we need? Thank!

    Hi,
    Please refer to following article and check the operating system requirements for SQL Server 2008.
    Hardware and Software Requirements
    for Installing SQL Server 2008
    Based on your description, I understand that you want to install the SQL Server on a DC.
    For security reasons, it is recommended that you do not install the SQL Server on a domain controller. So, it would be better if you put the SQL server on a second server or a virtualized server rather than on the SBS itself.
    You may encounter problems when installing SQL Server on
    a domain controller
    Using SQL Server in Windows Small
    Business Server 2008 Premium Edition
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • How to Install Coldfusion 8 64-bit on Small Business Server 2008 64-bit

    How to Install Coldfusion 8 64-bit on Small Business Server 2008 64-bit
    I ran Coldfusion 8 on SBS 2003 Premium for 6 months with no problems.  When we finally decided to cut over to SBS 2008, that’s when everything went to hell.  I tried for weeks to get Coldfusion 8 to install properly on the new SBS 2008 64-bit box.  During the course which, I found bits and pieces of information for Vista 64-bit and Windows Server 2008 64-bit installations.  There are some distinct differences, however, with SBS 2008 since it runs core Web applications like OWA, RWW and Companyweb.  After countless unsuccessful attempts, one of which completed corrupted the box, I found the solution.
    I have attempted in this white paper to detail the steps to assist others who may be in a similar situation.  I don’t make any warranty for the information, but so long as you follow the steps carefully you should be fine.  BTW, for those of you who say Adobe offers free technical support for licensed users, that’s not entirely true.  Like I said, I purchased CF8 and originally installed it on an SBS 2003 Premium box.  After we cut over to SBS 2008 and encountered problems, Adobe wouldn’t provide any technical support without charging.  Moreover, based on my initial conversations with Adobe’s technical team, no one seemed to know much about running 64-bit on SBS.
    From my understanding, only two versions of Coldfusion 8 can be installed in 64-bit: Enterprise and Developer.  The “normal” install (which I paid a grand for) can only be deployed in 32-bit mode – gee, THANKS Adobe!  By the way, in Developer mode only two distinct IPs can access the site in addition to the localhost.  Any additional IPs will result in a CFML error message stating that the maximum number of IPs have been exceeded.  At any rate, take your time and follow the steps to achieve a successful installation. 
    PRE-INSTALLATION TASKS
    Back Up SBS
    It’s always a good practice to backup your server before deploying any kind of major system changes.  Although this step is optional, I recommend it in case you need to restore your server for any reason.  Bear in mind, if your system ever gets totally corrupted, you cannot restore back from the twice daily incremental backup images alone.  You will need a full backup with system recovery information to restore.  Here are the basic steps:
    Click: Start > Programs > Administrative Tools.  Right-click “Windows Server Backup” and choose “Run as administrator”.
    Click “Backup Once” under Actions in the right-hand pane.
    Choose the “Different Options” radio button under Backup Options.
    Choose the “Custom” radio button.  What we’re primarily interested in here is backing up the OS – not your data partitions or attached drives.
    Select the “SYSTEM (C)” checkbox, uncheck any others.  Also, ensure that the “Enable system recovery” checkbox is selected before continuing on.
    Under ‘Specify Destination Type’, I usually select the “Local drives” radio button and point it to a Terrabyte USB drive I use for backups.  You can point this to a tape drive, or select the “Remote shared folder” radio button if you map to a UNC path to store your backup images.  Just remember, make sure that whatever path you select can readily be accessed in the event of an emergency.  Also, make sure the “Verify after writing (recommended)” checkbox is selected.
    Under ‘Specified Advanced Option’, I usually select the “VSS full backup” radio button instead of the default since I don’t use a 3rd party backup product.  If like me you rely solely on SBS for your backups, choose the full backup option.
    Confirm everything and click “Backup”.  This process may take several hours depending on the size of your system.
    Verify ISAPI Filters:
    In IIS Manager, double-click the server instance in the left-hand pane.
    In the center pane under IIS, double click the “Modules” icon to verify that the ISAPI native modules are already installed for IIS.  If it’s set up correctly you should see two entries:
    IsapiFilterModule              %windir%\System32\inetsrv\filter.dll
    IsapiModule                        %windir%\System32\inetsrv\isapi.dll
    If either of these modules are missing, you will need to re-install these (google for a solution).
    Set Up Development Environment
    Create a directory for your CFML files outside of the default Windows location (e.g., default is usually C:\inetpub\wwwroot\).  For the purpose of our install, I created a directory on a separate disk called: D:\DEV.
    Copy and paste your CFML files and directories into the new DEV root Web directory.  This will eventually be the directory where the Coldfusion installer places the CFIDE and CFDOCS folders. 
    Open IIS Manager and double-click the server instance in the left hand pane.  Expand the “Sites” folder.  Right-click the Sites folder and select “Add Web Site”.
    Enter a name in the “Site Name” box (e.g., “test-site”).  You will notice that the system will automatically create a corresponding Application Pool with the same name.  NOTE: this is important to prevent conflicts between the DefaultAppPool (needed for SBS Web apps like OWA, RWW, etc.) and the application pool needed for Coldfusion to function properly in SBS 2008.
    Point the “Physical Path” to the directory you created in step #1 above (e.g., “D:\DEV”).
    Don’t worry about testing the connection.  If you click “Test Settings” you may receive a warning that IIS cannot verify access to path (D:\DEV).  Don’t worry about this for the time being.
    Under “Host name”, enter a DNS path to your site (e.g., “dev.test-site.com”).  Click “OK”.
    Configure Application Pools for Installation
    In IIS Manager, double-click the server instance in the left-hand pane.  Click on “Application Pools” to display the list of server application pools in the center pane.
    In the “Actions” pane on the right-hand side, click “Set Application Pool Defaults”.
    Change “Enable 32-Bit Applications” - the second item from the top – from “False” to “True”, and then click “OK”.  NOTE: if you skip this step, Coldfusion will not properly create the required mappings during the install. We will change this setting back after the installation completes – more on this later.
    Modify the application.host.config File for 64-Bitness
    Click: Start > Programs > Accessories.  Right-click “Notepad” and choose “Run as administrator”.
    Open the config file from within Notepad – default location: C:\Windows\System32\inetsrv\config\applicationHost.config
    Do a search and change this one line from:
    <add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll" />
    To this:
    <add name="PasswordExpiryModule" image="C:\Windows\system32\RpcProxy\RpcProxy.dll" preCondition="bitness64" />
    Restart the IIS Admin service.
    Set HTTP Compression
    According to some threads I read, the http compression module can cause errors if you don’t disable it globally. To remedy this, perform the following:
    Click: Start > Programs > Accessories.  Right-click “Command Prompt” and choose “Run as administrator”.
    At the command prompt, change directory to intetsrv by typing: cd inetsrv
    Run the following command:
    C:\Windows\system32\inetsrv>appcmd.exe set config -section:system.webServer/httpCompression /-[name='xpress']
    This will turn off HTTP compression for all sites in IIS.
    In IIS Manager, double-click the server instance in the left-hand pane.  Double-click the “Compression” icon in the IIS section of the center pane.
    Uncheck all of the boxes, then click the “Apply” button under Actions in the right-hand pane.
    Recheck all of the boxes, then click the “Apply” button under Actions in the right-hand pane.
    Restart the IIS Admin service.  This should enable compression and coldfusion to work at the same time.
    NOTE: if for some reason you need to reverse this, run the following command from the command prompt:
    C:\Windows\system32\inetsrv\appcmd.exe set config -section:system.webServer/httpCompression /+[name='xpress',doStaticCompression='false',dll='%windir%\system32\inetsrv\suscomp.dll']
    INSTALLATION TASKS
    Download the 64-bit installation package from Adobe – filename: coldfusion-801-wind64.exe.
    Right-click the file and select “Run as administrator”.
    Accept the terms of the License Agreement.
    If you have an Enterprise license, enter it.  For our purposes, just click the “Developer Edition” checkbox.
    Select “Server configuration” – the default radio button.
    I deselected all subcomponents and can’t guarantee that you’ll arrive at the same results if you select additional items like “.NET Integrated Services”.  It should be fine, particularly if you install documentation.  My preference was to keep the install as plain vanilla as possible.
    Select the directory path for Coldfusion to install into – default is :C\Coldfusion
    THE NEXT TWO STEPS ARE CRITICAL TO YOUR SUCCESS.  Unselect “All IIS Websites” and select the “Configure specific IIS Website or another web server” radio button.  Click “Add”, and then select your test Web site (e.g., “test-site”) under “IIS Web Site”.  Hit “OK”.
    Do NOT use the default directory path for the CF Administrator location (e.g., default path: “C:\inetpub\wwwroot”).  Instead, point the installer to your new DEV root Web directory (e.g., “D:\DEV”).  The bottom line, you want the installer to place the CFIDE directory and files within this folder, alongside your other CFML files and folders.
    Enter an Administrator password.
    Choose to Enable RDS, or not.  I enable this by preference but it is not required.  This allows you to make updates to files using a CFML editor directly vs. having to move/FTP the files over if you’re working remotely.  Opponents to this argue that it’s potentially less secure, but for a lower environment I don’t see this as a major concern.
    Confirm everything to kick off the install.
    If all goes well you should see a message at the end stating that the install was successful.  I recommend you uncheck the box that asks you to open the CF Administrator in the default Web browser after the install.  NOTE: we will open it a different way during the post-installation tasks.  The worst thing that will happen if you forget to uncheck the box is that you might receive an error that the command prompt hung – not a big deal – just close it and move on to the next (final) steps.
    POST-INSTALLATION TASKS
    Verify CF Installation:
    The installation will create a new folder in your program group: Start > Programs > Adobe > Coldfusion 8.  The default “Administrator” link will not work because it points to the wrong path: http://127.0.0.1/CFIDE/administrator/index.cfm. The “127.0.0.1” or “localhost” path as you may recall in IIS, points by default to the “C:\inetpub\wwwroot” directory.  Our CFIDE files, however, are located within: D:\DEV.
    To bring up the CF Administrator logon page, open up a Web browser and replace the “http://127.0.0.1” part of the path with the DNS path name to your CF environment (e.g., http://dev.test-site.com/CFIDE/administrator/index.cfm).
    This should bring up the Coldfusion Administrator Login screen.  Enter in the Administrator password you created during the install to log in and configure your application server.
    Verify that your test-site renders correctly by typing in your test URL into a Web browser (e.g., http://dev.test-site.com).
    Fix Application Pool Defaults to Re-enable SBS Web Applications:
    At this point, Coldfusion Administrator and your test CMFL Web site should be working properly.  The problem is, default SBS Web applications like OWA, RWW and Companyweb will throw errors and fail to start.  Fortunately, this is easily remedied by performing the following steps:
    In IIS Manager, double-click the server instance in the left-hand pane.  Click on “Application Pools” to display the list of server application pools in the center pane.
    In the “Actions” pane on the right-hand side, click “Set Application Pool Defaults”.
    Change “Enable 32-Bit Applications” - the second item from the top – from “True” to “False” this time.  This should re-enable the SBS applications, which would otherwise result in 500 errors (e.g., OWA, RWW, Companyweb, etc.).  There is no need to restart IIS.
    Open a Web browser and test that you can once again connect to OWA, RWW and Companyweb successfully.
    In IIS click to highlight the application pool for your new site (e.g., “test-site”).  In the right-hand pane, click “Advanced Settings”.  Ensure that “Enable 32-Bit Applications” – second item from the top – is set to “True” for this application pool specifically.
    Lastly, jump up and down for joy!  Hopefully now, everything is working.  Best of luck!! ..Paul D (MCP).

    First, it would be a good idea for you to specify what distro of Linux you're using, as not all are supported by Adobe.
    Second, this is probably your problem right here:
    http://askubuntu.com/questions/40416/why-is-lib-libc-so-6-missing
    In a nutshell, CF expects the 32-bit version of libc.so.6 to be in /lib, but it's probably not. You might be able to modify the installer to point to the correct location for that file, or you might be able to create a symlink to the file - but as the above link describes, creating a symlink might have negative consequences.
    As for installing CF 8 64-bit, that's only available with Enterprise, not Standard. If you want CF Standard 64-bit, you need to upgrade to CF 9.
    Dave Watts, CTO, Fig Leaf Software

  • How to install Small Business Server 2008 in an existing Active Directory domain

    It is shown on this page:
    http://support.microsoft.com/kb/884453, "How to install Small Business Server 2003 in an existing Active Directory domain".
    Is it possible to do this with SBS2008 ?
    If "YES", are there any published information about the procedure ?

    Yes, it is. Thank you very much.
    But there is something that confuses me - I want to migrate from Win2003Std to SBS2008. And also, I want to keep the existing Win2003Std as a second DC for a long time.
    But it is written in the shown article:
    ... After the migration is finished, you must remove the Source Server from the network within 21 days. ...
    Is this rule mandatory for the scenarios where the Source Server is Std, not SBS ? As I know, I can have more than one DC(Win2003Std/Win2008Std) together with SBS2003. But what about SBS2008 ?

  • Email Encryption Small Business Server 2008

    We have are running Small Business Server 2008 with Exchange 2007. Our firm needs to have a look at email encryption. This is a relatively new concept that we are dealing with, we are a bit confused with how it works.
    Can the email encryption be set up on the SBS server? Or do we need to get 3rd party software installed onto the server?
    The emails need to be encrypted that go out of the office, our clients have a variety of email programs that they use.

    Hi,
    By using the TLS protocol, you can help improve the security of SMTP communication in Exchange 2007. Please
    refer to following article and check if can help you.
    How to Use TLS Authentication in Exchange
    2007 to Send and Receive Messages with Third-Party E-Mail
    If any update, please feel free to let us know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Warning: Palm OS Treos and Windows Small Business Server 2008

    If you use a Treo smartphone with the Palm operating system, beware:  it does not work with Microsoft Windows Small Business Server 2008.
    Palm acknowledges this failure and has no intention of fixing it. 
    There are at least two problems:
    (1) You must turn off all email security on the Exchange mail server to sync with Treos.
    (2) AutoSync locks up the Palm each time it occurs, and must be turned off.
    Here's the transcript of my chat w/tech support. After this, I spent a few hours on the phone and got the same answers.
    [12:35 AM] Gary says: Hello.
    [12:35 AM] Handoff connection active (1/5140).
    [12:35 AM] x says: Hi. Please see the question sent earlier.
    [12:36 AM] Gary says: Could you please be more specific about the issue?
    [12:37 AM] x says: Our Palms will not talk to Exchange Server 2007 unless all its security
    features are turned off. This is a problem with Palm/VersaMail. When will it be corrected?
    [12:38 AM] Gary says: Yes, that is true. I am sorry for the inconvenience this may have caused.
    [12:38 AM] Gary says: I am very sorry to inform you that currently we do not have any information on this.
    [12:39 AM] x says: Apology accepted and appreciated. But when will this be fixed?
    [12:40 AM] Gary says: Unfortunately we do not have any sort of update on this. I suggest you to post the
    feedback in the Palm Website.
    [12:41 AM] x says: Okay, next question:  Every AutoSync locks up the Palm, so we have to turn
    AutoSync off. Do you intend to rectify this problem?
    [12:42 AM] Gary says: I understand your concern. Is it happening with all the Palm devices?
    [12:42 AM] x says: Yes.
    [12:43 AM] Gary says: Do you receive any error message before locking up the Treo?
    [12:43 AM] x says: No.
    [12:46 AM] Gary says: Okay, as this happening with all the devices to me it looks like the issue should be
    diagnosed closely to find the root cause. Was this happening with the Exchange Sever 2003?
    [12:46 AM] x says: No
    [12:46 AM] Gary says: So, the AutoSync feature is Locking the device from the day you upgraded to the
    Exchange Sever 2007.
    [12:46 AM] Gary says: Am I correct?
    [12:47 AM] x says: yes.
    [12:48 AM] Gary says: Okay, as this is the issue related to the sync with the Exchange Server 2007 and the
    AutoSync to find out the root cause I will escalate this issue to our escalation channel which is our Voice
    Support Team.
    [12:48 AM] Gary says:
    I will provide you all the information and guide you in the correct direction to address this issue.
    [12:48 AM] Gary says:
    I suggest you to get in touch with the Voice Support and I am sure they will fix the issue.
    [12:49 AM] Gary says:
    I will provide you a Service Request, when contacting the Voice Support, provide this Service Request Id and you will get a free Technical Support.
    [12:51 AM] Gary says: Please provide me your Last name, First name, complete address, phone number,Email address, date and place of purchase of device and serial number of the device to create a Service Request Number.
    [12:51 AM] x says: Of course I provided all this when I logged in, but here it is again:....
    [12:54 AM] Gary says: Thank you for providing all the information.I need 5 minutes to register the device and create a Service Request.
    [12:55 AM] x says: Thanks for your help, and confirmation of the incomprehensible failure to support Exchange Server 2007.  We're this close to dumping these things if this is the kind of tech support Palm intends to provide.
    [1:00 AM] Gary says: Thanks for staying on hold: I am sorry for the delay. I can understand the inconvenience you are facing.
    [1:01 AM] Gary says: Based on the information you provided, I created a service request for you in our database.  The Service Request number is : 1-51558238041
    [1:01 AM] x says: Will I get an email?
    [1:01 AM] Gary says: Using this service request number, you need to contact our Voice Support department.  Voice Support Department number is 877-426-3777. Voice support will be available from  5:00AM to 9:00PM (PST) on weekdays and from 8am - 5pm PST on weekends.Please note down the above given Service Request Number and Voice Support Number or else you will lose this information once the chat session is closed.
    [1:02 AM] Gary says: Yes, I will email this chat session to you.
    [1:02 AM] Gary says: Is there anything else I can assist you with today?
    Post relates to: Treo 755p (Sprint)

    The problem is the default security profile isn't compatible. You can go into the Power shell command line and remove the default activesync mailbox policy.
    Post relates to: None

  • Outlook 2013 Constantly Prompting For Credentials - Exchange 2007 - Small Business Server 2008

    Hello, I am having a problem using Windows Small Business Server 2008 and Exchange 2007 with Outlook 2013. The issue is that a credentials box appears in Outlook 2013 when using there exchange account whilst connected to the domain. The box will randomly
    prompt for user credentials, once the user credentials are entered it will either pop back up again and if you enter the details in again it will continue to pop up for around 4 or 5 times before accepting the credentials. It will then pop back up within 15
    minutes and do the same thing, if you click "Cancel" on the box it will also go away and remain connected to exchange however a popup in the bottom right will appear asking for a password even though you can send / receive from the mailbox.
    I have looked into this issue for hours and hours and still can not find a resolution, I have tried re-installing Office 2013 and re-creating the Outlook Profile as-well as as the Windows 7 Profile. I have checked through all the SSL certificates in IIS
    and everything appear to be correct.
    Is this a common issue? Is there anything I can do to further diagnose or fix this issue without having to try to re-install both the server and machine?

    Hi James_wilson,
    Any update?
    Just additional, would you please let me know whether have installed all updates for Outlook 2013? If hasn’t, please install and then monitor the result.
    Please also check if you enable
    Always prompt for logon credentials setting in Outlook 2013. 
    If you enable this setting, please uncheck and check if this issue still persists. Meanwhile, please remove the old credential in
    Credential Manager, then add again. Then monitor the result
    By the way, please run the Exchange BPA on the SBS 2008 server and check if can find some issue.
    Hope this helps.
    Best regards,
    Justin Gu

  • Windows Small Business Server 2008 shutdown 180days 38 4

    Hello to everyone, 
    I'm trying to solve a problem in a friend server.
    i'm working on a Small Business Server 2008, it's a DC, NO sharepoint, NO Exchange (there is another software), NO DHCP (firewall do it), WINS and DNS enabled.
    Some days agoo Server has shutdown and in event viewer i found this 2 errors:
    38 and 4
    Event ID 38:
    "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 68 day(s) 19 hour(s) 30 minute(s). Please look
    for additional events for Additional Server Count Check to troubleshoot."
    Event ID 4:
    "The Additional Server Count Check in the Licensing component did not pass because error 0x8007200a occurred in function f1031 [PFVK]. 
    The specified directory service attribute or value does not exist.
    I tried slmgr.vbs -dli and it's Licensed correctly.
    So i ran dcdiag /q and i've seen many errors like this:
    EventID: 0x0000168F
    Deleting dynamic of the DNS record '_kerberos._tcp.dc._msdcs.dominio.local. 600 IN SRV 0 100 88 server.dominio.local. 'failed on the following DNS server.
    I ran dcdiag /fix but problem still remains. 
    I really don't know how to fix this issue...
    Anyone have an idea?
    I also thought to use, in the extreme case, -ream , like slmgr.vbs -rearm, but i don't know how many times i can rearm server.
    Thank you and have a nice day

    Here you are DCPromo Log, it's in Italian 'cause is an Italian Server, btw i can translate.
    Controllo dell'installazione dei file binari di Servizi di dominio Active Directory in corso...
    Installazione Servizi di dominio Active Directory
    Convalida dell'ambiente e dei parametri in corso...
    Impossibile creare una delega per questo server DNS perch‚ la zona padre autorevole non Š stata trovata oppure non esegue il server DNS Windows. Se si sta effettuando l'integrazione con un'infrastruttura DNS esistente, Š consigliabile creare manualmente una delega per il server DNS nella zona padre per garantire una risoluzione dei nomi affidabile dall'esterno del dominio nameserver.local. In caso contrario, non Š necessario eseguire alcuna operazione.
    Verranno eseguite le azioni seguenti:
    Configurare il server come primo controller di dominio Active Directory in una nuova foresta.
    Il nome del nuovo dominio Š nameserver.local e corrisponde anche al nome della nuova foresta.
    Il nome NetBIOS del dominio Š nameserver
    Livello di funzionalit… foresta: Windows Server 2003
    Livello di funzionalit… dominio: Windows Server 2003
    Sito: Default-First-Site-Name
    Opzioni aggiuntive:
    Controller di dominio di sola lettura: No
    Catalogo globale: S
    Server DNS: S
    Crea delega DNS: No
    Cartella database: C:\Windows\ntds
    Cartella file di registro: C:\Windows\ntds
    Cartella SYSVOL: C:\Windows\sysvol
    Il servizio Server DNS verr… configurato in questo computer.
    Il computer verr… configurato per l'utilizzo di questo server DNS come server DNS preferito.
    La password del nuovo amministratore di dominio Š identica alla password dell'amministratore locale di questo computer.
    Avvio in corso...
    Verifica della necessit… di installare Console Gestione Criteri di gruppo in corso...
    Premere CTRL+C per: Annulla
    Configurazione del computer locale per l'hosting di Servizi di dominio Active Directory
    Creazione della partizione di directory: CN=Schema,CN=Configuration,DC=nameserver,DC=local in corso. Oggetti rimanenti: 1585
    Creazione della partizione di directory: CN=Configuration,DC=nameserver,DC=local in corso. Oggetti rimanenti: 1250
    Creazione della partizione di directory: CN=Configuration,DC=nameserver,DC=local in corso. Oggetti rimanenti: 966
    Creazione della partizione di directory: CN=Configuration,DC=nameserver,DC=local in corso. Oggetti rimanenti: 739
    Creazione della partizione di directory: CN=Configuration,DC=nameserver,DC=local in corso. Oggetti rimanenti: 535
    Creazione della partizione di directory: CN=Configuration,DC=nameserver,DC=local in corso. Oggetti rimanenti: 367
    Creazione della partizione di directory: CN=Configuration,DC=nameserver,DC=local in corso. Oggetti rimanenti: 204
    Creazione della partizione di directory: CN=Configuration,DC=nameserver,DC=local in corso. Oggetti rimanenti: 57
    Creazione della partizione di directory: CN=Configuration,DC=nameserver,DC=local in corso. Oggetti rimanenti: 0
    Creazione di oggetti Servizi di dominio Active Directory nel controller di dominio Active Directory locale
    Impostazione delle informazioni sul criterio LSA
    Impostazione della radice del nome DNS del computer a nameserver.local
    Protezione in corso di machine\software\microsoft\windows
    Protezione in corso di machine\system\currentcontrolset\control
    Protezione in corso di machine\system\currentcontrolset\control\class
    Protezione in corso di machine\system\currentcontrolset\services
    Protezione in corso di c:\windows\system32\spool
    Operazione sul controller di dominio completata.
    Configurazione del servizio Server DNS nel computer in corso...
    Installazione di Servizi di dominio Active Directory completata in questo computer per il dominio nameserver.local.
    Questo controller di dominio Active Directory Š assegnato al sito Default-First-Site-Name. Ô possibile gestire i siti con lo strumento di amministrazione Siti e servizi di Active Directory.
    I controller di dominio Windows Server 2008 hanno un nuovo valore predefinito, pi— sicuro, per l'impostazione "Consenti algoritmi di crittografia compatibili con Windows NT 4.0". Il valore impedisce che "client" Microsoft Windows e non Microsoft SMB usino algoritmi di crittografia vulnerabili di stile NT 4.0 per stabilire sessioni su canale sicuro con controller di dominio Windows Server 2008. Ne consegue che operazioni o applicazioni che richiedono un canale sicuro gestito da controller di dominio Windows Server 2008 potrebbero non funzionare.
    Le piattaforme interessate dal cambiamento sono Windows NT 4.0, i "client" non Microsoft SMB e dispositivi NAS che non supportano algoritmi di crittografia pi— avanzati. Ci sono inoltre conseguenze per alcune operazioni in client che eseguono versioni di Windows precedenti a Vista con Service Pack 1, come l'aggiunta a un dominio effettuata dall'Utilit… di migrazione ad Active Directory o da Servizi di distribuzione Windows.
    Per ulteriori informazioni, vedere l'articolo 942564 della Microsoft Knowledge Base all'indirizzo http://go.microsoft.com/fwlink/?LinkId=104751.
    Ô necessario riavviare il computer per completare l'operazione.

Maybe you are looking for