How many changes should be taken when an application is migrated from server 2003 to server 2008 RRS feed

  • Question

  • Hi,

    We have an application software, which is implemented based on MFC in IDE Visual C++ 6.0 (for Client) and Visual studio 2005 (VC++ 8) on Windows Server 2003(32bit)(for Server and client) and Windows XP (for client only). In this application, WinSNMP, RPC, UDP socket, ADO (SQL Server 2000) and Windows Message techniques have been used, and at the same time, some thirdparty software are be used, such as Rogue Wava Stingray Studio 2002, VSFlexGrid Pro 7. In addtion, this application is managed by EMC Legato Automated Availability 5.1.2 (will update to 5.3). This application will be installed an InstallShield which unify the installation of EMC Legato Automated Availability, MS SQL Server 2000 and this application software.

    Now we will migrate this application from Server 2003(32bit) to Server 2008(32bit), Could guys here answer my the following questions:
    1. can the IDE (Visual C++6.0 and Visual studio 2005) still be used on Windows Server 2008?
    2. What must be change for this migration on application software, thirdparty software and installshield?

    I'm a necomer and perhaps these questions are simple for you. I will appreciated for any direction.

    Thursday, November 12, 2009 5:57 AM

All replies

  • Hi,

     try this one it may help for you!!

    Visual Studio 2005 Service Pack 1 Update for Windows Vista,Windows 7, Windows Server 2008, and Windows Server 2008 R2.

    Brief Description

    The Visual Studio 2005 Service Pack 1 Update for Windows Vista addresses areas of Visual Studio impacted by Windows Vista enhancements. This update also applies to Windows 7, Windows Server 2008, and Windows Server 2008 R2.

    try to download the Service pack 1 for VS 2005 from here

    Installation Instructions

    1.   Before you install this update, it is highly recommended that you read the Visual Studio 2005 Service Pack 1 Update for Windows Vista Release Notes.

    2.   If the machine participated in the Visual Studio 2005 Service Pack 1 Update for Windows Vista Beta, please be sure to uninstall the beta first.

                            i.      Go to Control Panel > Programs > Programs and Feature > Installed Updates.

                           ii.      Select 'Hotfix for Visual Studio 2005 [SKU name] - ENU (KB929470)' or 'Hotfix for Visual Studio 2005 [SKU name] - JPN (KB929471)'.

                          iii.      Right-click and select 'Uninstall'.

    3.   Download the Visual Studio 2005 Service Pack 1 with Vista Support Update installer executable file locally.

    4.   Right-click the downloaded file and select ‘Run as Administrator’.

    if you are migration on application software from windows server 2003 to Windows server 2008(Content for the developers point) Check the Following features.....

    Quick Compatibility Check
    Operating System Versioning
    User Account Control (Standard User Changes)
    UAC: Application Update Guidelines
    UAC: COM Per-User Configuration
    Windows Resource Protection (WRP)
    Internet Explorer Protected Mode
    Windows 64-bit
    IIS 7
    Microsoft Graphical Identification and Authentication (GINA)
    Session 0 Isolation
    Networking: TCP/IP Stack and the Windows Filtering Platform
    Networking: Kernel Mode IP Helper APIs
    Networking: IPv6
    Compatibility Risks
    Windows Display Driver Model
    Default Programs
    Program Compatibility Assistant (PCA)
    Graphical Device Interface GDI
    User Interface Privilege Isolation (UIPI)
    High DPI Scaling
    PNG Icons
    Named Pipe Hardening
    SPAP Deprecation (Pstore)
    WMI Providers: Default Security Hosting Model
    Volume Shadow Copy Service
    Standard User Analyzer
    DHTML Editing Control
    Help Engine Support
    Junction Points and Backup Applications
    Application Compatibility for Backup and Recovery
    Integrating with the Search the Internet Feature
    MMCs Must Be Data Execution Protection (DEP) Aware
    Networking: Turning off the Windows Firewall
    Issues Relevant to Windows Server Codename "Longhorn"
    Active Directory Changes in Windows Server Codename "Longhorn"
    Windows Server Codename "Longhorn" Roles
    Windows Application Experience in Windows Server Codename "Longhorn"
    Windows Server Codename "Longhorn" Server Core
    Windows Server Failover Clustering on Windows Server codename "Longhorn"
    Networking: Windows Firewall Enabled by Default on Windows Server codename "Longhorn"

    for more information you can check the


    Anil Inampudi



    • Proposed as answer by Anil Inampudi Monday, December 14, 2009 2:42 PM
    Friday, November 20, 2009 2:45 PM