I am specing out new development workstations for my team and I am running into a conflict. I am a developer and I want Windows Server 2008 R2 because that is what our production servers are running. The IT guys want to give us Windows 7 because that is where they have tested all their infrastructure.
My question is this: is there enough of a difference between the two to push for 2008 R2? I know MSFT has crippled IIS in previous versions of Windows unless it was the server edition so I am skeptical about Win7 giving me what we need.
You can use Windows 7 for your development machines and have one Windows Server 2008 R2 for UAT deployments. This way you can have the best of both worlds. IT will be happy that you are all running Windows 7 and you will be happy that you're able to test your application in windows server 2008.
This question answer might be helpful.
Differences between Windows 7 and Windows Server 2008 R2
Your IT guys are correct aside from licensing issues such cost as Office without workstation on OpenValue, OpenSelect etc.. (remember they are packaged together) etc.. there are hardware issues and compatibility with future software.
There is no way you need 2008 R2 Server, do you want to work in the data center too? or have a full copy of the live database? You should have a CI server though that represents the live environment , the IT guys should provide this for you - probably as a VM.
Related
Has anyone had experience installing Foswiki on windows in the past couple of years? It unfortunately seems that all the guides are extremely old and vague.
The setup on my target machine is Windows Server 2012, Activestate Perl, and IIS 10. The machine is a company server, so I cannot change the setup or install another web server like Apache.
Sorry, I don't think that these are suitable preconditions: there are too many gotchas, too few people that ever went that route, it will cost you lots of efforts and the result will be inferior. There are two alternatives: (1) convert the machine to a Linux server or (2) grab the VM from https://foswiki.org/Download/FoswikiRelease02x01x04 with a pre-installed Foswiki ready to go.
Does anyone have an idea if it is possible to downgrade IIS version 7 to lower version of IIS on windows server 2008?
I have an ASP program on win 2000 server and I am planning to migrate this program on new setup on better hardware and software but I am getting HTTP 500 which in detail error logs I see complain of classic asp and IIS 7. In my case obviously the the ASP used (by another programmer) is and old classic ASP platform and now with this conflict I cannot get my web sever operating properly.
Any help/idea would be really appreciated.
Thanks,
Alan
Azure service configuration allows to alter osFamily. Currently there're two options. Value 1 (the default) selects Windows Server 2008 and value 2 selected Windows Server 2008 R2.
I'm currently with the default (2008).
What changes should I expect if I just change to R2? Will it be faster? Will anything likely break?
You should see this as if you were upgrading from Windows Vista to Windows 7, as described in this question: What's the difference between Windows Server 2008, 2008 SP2 and 2008 R2?.
If you're building web applications the largest impact will probably come from IIS. Windows Server 2008 uses IIS 7.0, Windows Server 2008 R2 uses 7.5. Read about the differences here: What's New in the Web Server (IIS) Role (IIS 7)
There's also a whitepaper that describes the new and changed functionalities and features: Changes in Functionality in Windows Server 2008 R2.
To answer your question if anything will break I would say no (although something could always go wrong). I've deployed many applications to Windows Azure and this never caused issues for me. When I upgraded from Windows Vista to Windows 7 it felt like I was using a more mature, stable and better performing system, and I would dare to believe the same applies to the server releases. And advantage is that you'll have new features available, like the Win32 support to mount VHD files (I think this relates to your VHD question).
I am about to install SharePoint Foundation for development purposes on my Windows 7 x64.
I will be using Visual Studio 2010.
Beside other things, MS site says:
If you use Windows 7 or Windows Vista for your development environment, you should have access to a test environment that has the same operating system installed as your production environment.
I am not sure what does it exactly mean by "you should have access to test environment"?
Will I be able to compile, run debug and test web parts and other stuff?
Are there any significant limitations for Win 7 and SP Foundation for development?
Since SharePoint production OS should be win2008+ by saying "the same operating system" they mean win2008+, neither win7 or Vista should be used as testing servers. This passage means that there should be another server that will be win 2008 and will host SharePoint and this server should be the one you should test your solutions on.
p.s. yes. there are some low level differences between sharepoint hosted on win7 and win 2088. but you will be able to do all the stuff you want on win 7 too.
Migrated an apps to Windows Azure - previous platform was windows server 2008 R2. When I try to configure os it gives me two options with Windows Server 2008 SP2 being default. Are there any known issues of selecting Windows Server 2008 R2? Any performance implications. I was assuming that since R2 was released later and had some enhancements related to virtualization etc it should be better.
Yes, I'd go for Windows Server 2008 R2, which is based on the Windows 7 kernel rather than the Vista kernel used by Windows Server 2008 SP2.
I'd expect that Microsoft make the 2008 SP2 option available for Azure customers that have not yet tested their applications under the newer platform.