Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I have been asked to look at the feasibility of migrating an ASP app from Windows 2003 to Windows Server 2008 R2.
Old setup:
ASP Classic Hosted on: Windows Server 2003 DB: SQL Server 2000
Proposed new setup:
ASP Classic Hosted on: Windows Server 2008 R2 IIS: 7 DB: SQL Server
2008
Ideally the app should be re-written in ASP.NET, but the company doesn't have the budget for this right now.
Questions
Would it be possible to host Classic ASP built on Windows 2003 w/ IIS 6 on a Windows 2008 R2 w/ IIS 7.5 environment?
What steps can be taken to successfully migrate the application and database from the old environment to the new environment.?
Would it be possible to host Classic ASP built on Windows 2003 w/ IIS
6 on a Windows 2008 R2 w/ IIS 7.5 environment?
Classic ASP can be hosted on Windows 2008 and 2012. As of IIS 7, Classic ASP is no longer enabled by default. See this article.
How to enable Classic ASP module in Windows 2008
Click Start, point to Administrative Tools, and then click Server
Manager.
In the Server Manager hierarchy pane, expand Roles, and
then click Web Server (IIS).
In the Web Server (IIS) pane, scroll to the Role Services section, and then click Add Role Services.
On the Select Role Services page of the Add Role Services Wizard, select
ASP.
What steps can be taken to successfully migrate the application and
database from the old environment to the new environment?
32 bit vs 64 bit components - 32 bit dlls do not work in 64 bit application pool. Make sure your Application Pool is set accordingly.
Classic ASP uses "Classic .NET" setting in the application pool
Verify your supporting dlls e.g. "Persits ASPemail" work in Windows 2008 R2. In some cases you may need to upgrade your license.
Take a look at this post to assist with SQL Server 2000 to 2008 migration.
Related
I would like to create a server infrastructure for SharePoint Server 2013. We would like to buy 2 servers, which the first one will be a domain controller and on the second there will be a SharePoint Server. Now I am thinking about Windows Server version to buy. I would like to buy Windows Server 2012 Standard R2, which will be installed on a domain controller server. On the SharePoint server I am planning to install Windows Server 2012 Essentials R2.
We will have about 100 CAL licences on AD.
The question is if it will work with Essentials server.
Thank you for you answers.
Please look at the Microsoft SharePoint Requirements page -> https://technet.microsoft.com/en-us/library/cc262485.aspx
In general it will work. The problem is the CAL number. With Essentials you can only have a max number of 75 CALs.
Here is also a good article about that topic: http://www.sbsfaq.com/?p=3617
This new Windows Server 2012 Essentials however is different again – it’s designed with a limit of 25 users. After that you need to
break it out into the normal Windows Server products with the normal
Windows Server CALs.
I have developed a POS System Recently and workin on its deployment.
Application Specifications:
The application is basically a POS system.
Back end = SQL Server 2008 Express R2.
Front End = C#
I also used SMO libraries.
Deployment Method = Click-once.
Target Framework = 4.0.
Development Tool = Visual Studio 2012 RC.
OS = Windows 7 Home Premium.
Used some SQL feature packs like Shared management Objects, CLR types. and others.
The prerequisites are selected and i packaged them also.
In brand new windows 7 the installation was fine. and application is running upto date.
In win XP the installation is fine. but when i start the app. it colses with this error.
SQL Server database is not installed and or not running.
and application quits.
IMPORTNAT NOTE:
THE 'WINDOWS XP SP3 PROFESSIONAL'
ON WHICH I AM TESTING IS INSTALLED ON VIRTUAL MACHINE
In the code i am running some SMO library functions in order to install *.sql script for the application's first time use.
SQL Server 2008 R2 is installed with all of its dependencies. and other feature packs. All the prerequisites are installed on XP.
Can you run SQLServer Management Studio on the XP VM and see SQLServer? If you run the SQLServer Configuration Manager on the VM, and click on SQL Server Services, does it show the service is running?
How do you have the connections configured? Do you have named pipes and TCP/IP enabled for the SQLServer Network configuration? What about the SQL Native Client configuration?
Do you have SQLServer Express ticked as a prerequisite in the ClickOnce deployment? What happens if you run setup.exe? Does it recognize that it's installed?
The SQLServer Express that's installed -- is it a named instance, or did you leave it as ".\SQLExpress" ? Id the connection string being used by the ClickOnce application right?
We just moved one of our .Net applications from a Windows 2003 Server to a virtual Windows Server 2008 R2 (64Bit, VMWare).
This application is a simple console application running on .Net Framework 4.0, 32Bit, that runs different jobs to select, modify and save business data to a database. For the database we use SQL 2008 R2.
Since we run the application on the Windows Server 2008 R2 we recognized, that the execution of Select-Statements with LINQ to SQL are slower than on the Windows Server 2003 we used before. We checked it with a simple LINQ Query, and that tooks about 500 milliseconds longer on Win 2008.
We use the System.Data.Linq.DataContext and get Objects from the Database with the Method GetTable<>().
To compare the duration we took the time from creating the datacontext until the mapping from the DB-Objects back to the .Net-Objects in the application.
See the code:
System.Data.IDbConnection testConnection;
System.Data.Linq.Mapping.MappingSource testMappingSource;
...
...
using (System.Data.Linq.DataContext dc = new System.Data.Linq.DataContext(testConnection, testMappingSource))
{
dc.DeferredLoadingEnabled = false;
return = (from dbObject in dc.GetTable<TestTable>()
select dbObject).FirstOrDefault();
}
On the Windows 2008 R2 Server, the .Net Framework 4.0 is installed, and in the server features the .Net Framework 3.5.1 Features are enabled.
The application was installed on three different stages (Dev, Test, Production) on three Windows 2003 Server. Now it runs on three virtual Windows 2008 R2 Server. We have the same Problem on all three Windows 2008 R2 Server. And we even tested it on a physical Windows 2008 R2 Server; same Problem there.
Has anyone an idea what causes this difference? And what may be a solution to resolve this problem?
Thanks a lot in advance!
Greets
Tom
I am about to create a new developer PC image for developing WPF applications using VS2010, WCF, SQL2008 and SharePoint2010.
What OS should I opt for? Windows 7? Windows Server 2008 R2?
I'd have thought Windows 7 to make sure that I have a similar experience during development as an end user, however I can't install SharePoint on a client OS and so thought about Windows Server 2008 R2 to help with the SharePoint development process.
Thoughts?
I'd recommend Win 7, because your operating system is developed for interaction not serving. There is lots of things in a server OS that you don't need.
However if you are in a VM environment I would recommend that you add a VM for a server with the appropriate software for them to play with (Sharepoint, SQL etc.) so that their dev environment not slowed down by the server's they need to fire up for development.
Are there any limitations with respect to developing ASP.NET and WPF apps using VS 2008/2010 and SQL Server 2008 on Windows 7 Home Premium?
I know you can run IIS 7.5 on Home Premium. I Googled and Binged on Home Premium and VS/SQL Server and couldn't find much. It doesn't look like the features missing from Home Premium, domain joining, xp mode, etc... shouldn't prevent one from running and developing in VS/SQL Server.
Update
I did discover one limitation w/IIS 7.5 and it applies to all versions of Windows 7 I think. You can't create your own self signed SSL certificate specifying a name other than the machine name. You're stuck with your machine name which isn't that big a deal, but it is a change from previous versions.
Update II
You can't do remote debugging on Home Premium. msvsmon won't run at all. I can't even get it to do remote debugging natively.
Visual studio will run fine. You will be "limited" to either SQL Server Express, or SQL Server Developer edition as the mssql installer checks the OS version and will refuse to install the higher end editions on desktop OSes. Note that developer edition is the exact same as the higher end editions, except with a different license, you can only use it for development, not to run real databases.
Yes, you can, and you won't have any trouble with it.
In general, application compatibility is not affected by the edition (not version) of Windows.
I would consider what the target infrastructure (Windows/IIS, .net, SQL Server etc versions) would be if you want to deploy it...