- #Windows server 2008 r2 64 bit install
- #Windows server 2008 r2 64 bit 64 Bit
- #Windows server 2008 r2 64 bit driver
- #Windows server 2008 r2 64 bit 32 bit
- #Windows server 2008 r2 64 bit upgrade
But for now, let's start with the basics. We will take a closer look at two of those new features, Remote Desktop Services and DirectAccess, in the coming weeks. But it presents some new and genuinely interesting ways of solving a lot of the day-to-day issues, big and small, that the busy IT person deals with.
#Windows server 2008 r2 64 bit upgrade
It has a revised kernel, it has a new user interface, and it isn't a drop-in upgrade for that entry-level server you bought six years ago. Server 2008 R2, on the other hand, is a much different story. Windows Server 2003 R2 certainly fit that description-the kernel, core operating system and feature set of Server 2003 were 100 percent retained for 2003 R2, and some useful tools were added on. Maybe it's supposed to appeal to the inner Star Wars fan and make you think it's an adorable sidekick that can solve difficult problems with a simple tool. This "R2" moniker has gained favor in Redmond in the last few years as a way of saying, "It's the same software, honest! We've nailed on some bits to the side." It's supposed to appeal to IT departments that are allergic to disruptive changes. That alone is enough of a condemnation to keep plenty of people away, even before we get to the learning curve.īut when you start to take a closer look, you realize that something much bigger is going on here than the name suggests. Plus, you're busy! So when you hear the name "Windows Server 2008 R2," what's your first thought? You're likely to believe that it's little more than a warmed-over service pack for Windows Server 2008, which is the server version of the much-maligned Windows Vista. Chances are very good you're still using XP on the desktop and Server 2003 in the closet, because you're used to it, you're comfortable with it, your users understand it, and nobody's paying you to be disruptive.
I know this sounds bad, but in practice it isn't that difficult.Let's say you're the sort of IT person whose days, evenings, and weekends are consumed by running around from point to point, trying to keep your company's or clients' computers running.
Robocopy must be run from an administrative command shell, and even so, you may need to resort to using subinacl to make sure administrators have file level permissions for the entire drive. If paths change you can always go back into the registry to change the paths and still retain your share permissions from the old server. So d:\share on the old server is d:\share on the new server. Viola! I'm assuming here that the paths for the shares from the old server to the new server won't change.
#Windows server 2008 r2 64 bit 32 bit
At that point just export your shares from the registry of the 32 bit server, import the registry key on the new server, and restart the server service. inf file to ensure that they do.įor files and printers: if you don't want to use DFS (which we don't,) it's easy enough to robocopy the data.
#Windows server 2008 r2 64 bit driver
Some vendors are not very good about making sure the driver names match, and at that point you'll have to hack the.
#Windows server 2008 r2 64 bit 64 Bit
Also, the driver names for the 32 and 64 bit versions **must match exactly** If they don't, the print server won't recognize it as an additional driver for the same printer. I've heard this can be avoided by having a windows 7 32 bit installation point handy, but I've never personally been able to get that method to work.
#Windows server 2008 r2 64 bit install
It is *very* important to go back into the advanced settings of your newly shared printer to add the 32bit drivers if you still have 32 bit clients (which you probably do.) This part can also be problematic: at times 2008 will not allow you to install the 32 bit driver from the console and you have to add the driver by connecting to the server from a 32bit OS.
Run through the printer installation, create your port and select your driver. What I have found to work the best is manually recreating the printers. If 2008 happens to have the 64 bit drivers for the printers you are migrating, it will recreate the printers, but then you'll need to go back and add 32 bit drivers. In my experience, it usually just ends up recreating your ports for you- and not much else. You can use the print migration functions built into 2008, but having it work 100% is problematic. It looks like you can do it either with a command line utility or via the print management admin tool.įor the print server, migrating from 32 bit to 64 bit is a pain in the ass. One way you could do it would be to set up Distributed File Shares, let it fully replicate, then remove the old server from the DFS targets list and disable the shares.įor the printers, you want this. I had to do the same a few months ago and it was a pretty easy process.Īs for files and shares.