One of our customers has 1 (Virtual) Windows server 2008r2 enterprice server which is a root DC with Exchange 2010 sp1.
They want to upgrade Exchange to SP3 so they can easily migrate to Office 365.
Since there is no proper backup and according to Microsoft there is no way to rollback after installing SP3, I'm not comfortable to just go ahead and upgrade.
The idea is now to install a second Exchange 2010 server but one with SP3, migrate or sync the mail database to temporary have a redundant setup. Then when all is synced, the 'old' server can be upgraded to SP3 as well, and the new server can be taken offline.
Is this the right approach?
Regards,
Related
The TeamCity website reports that the software is compatible and tested with Windows Server 2008 and not on Windows Server 2008 R2 or 2012/R2. Has anyone deployed TeamCity on Windows Server 2012 R2 ? Is there any known issue that we need to be aware of? Will the customer service team support queries on Windows Server 2012 R2?
TeamCity site's System Requirement page
Windows Server 2012 R2 is fully supported.
I have set-up three different build servers on Windows Server 2012 R2. There is no known issues.
I have also used Microsoft SQL Server with TeamCity. (here's a tutorial http://log.ld.si/post/teamcity8-sql-server).
They will support queried ofcourse :)
It could be that what I'm trying to achieve isn't possible (as I can't find out how to do it!) but basically I've upgraded my VS Version from 2010 to 2013.
All of my companies test sites are running on IIS 6 on Windows 2003 Server.
And what I'm trying to do is remote debug my solutions on this machine (Which I was able to do in VS2010).
So my question is...is this possible or will I need to convince someone to upgrade the server?
Thanks,
Craig
I am doing a custom install of Visual Studio 2010 onto a new development box.
The target machine already has SQL Server 2008 R2 SP1 installed.
I see one of the components is SQL Server 2008 Express Service however this machine already has SQL Server installed on it. Its a 1.6 GB disk space savings plus I dont like to add unnecessary services (or installs) if I do not have to.
So my question is, would I want to still install the "express service" even though I have the full Developer Version of SQL Server 2008 R2 already installed? And if so, why? Is there a future benefit or is this somewhat redundant and can I save space and keep this box better tuned?
Just wanted to update this as I eventually learned that I did not need to install the express service of SQL Server 2008 because I already had the full developer version installed. There have been no ill effects and I was able to save the disc space required for the express service plus the RAM needed to run and maintain that instance.
c:\inetpub is there, but not the subdirectory: mailroot\
I recently installed a new HP server computer with Windows Server 2008 R2 Foundation pre-installed.
Should \mailroot\ automatically be installed, or is this a manual step?
It is needed for sending and receiving email to/from the web apps that I'm
hosting on the server; web apps written in Visual Basic 2010, etc.
I have my own Windows Server 2008 R2 server and I have no mailroot directory there either. I would assume that this is not an automatically installed component.
Perhaps How to: Install and Configure SMTP Virtual Servers in IIS will be of some help.
I wanted to get some feedback about the problems we might face if we deploy Sharepoint 2007 on Windows 2008 instead on windows 2003
Windows SharePoint Services 3 is supported just fine on Windows 2008. You'll need to make sure that you're using SP1.
See answers on ServerFault:
Installing Office SharePoint 2007 on Windows Server 2008 R2?
Installing Sharepoint 2007 on Windows Server 2008 R2
To save you time two main points of the solution are:
Create your own slip-streamed installation of SharePoint with the latest Service Pack included (SP3 at the moment) and then install this directly onto Windows Server 2008 R2.
Activate .NET Framework 3.5.1 feature in Windows Server to get rid of the Windows Workflow Foundation error