2008 R2 - Don't rush!

[john]

Try the following:

 

On the DC, I opened up the Group Policy Management tool and changed the following:

 

Computer Configuration\Policies\Administrative Templates\System\Net

Logon\Allow Cryptography Algorithms Compatible with Windows NT 4.0 -> Enabled

 

I then ran a gpupdate /force.

 

Set that as your Default Domain Policy so EVERYTHING gets it and reboot it all a few times and do the same to the clients etc and see if that helps I suspect it will help.

[DMcCoy]

I have already changed the NTLM session security, as well as allowing the NT4 compatibility last year when I moved to 2008 (Smoothwall broke when I went to 2008 too).

 

Neither have had any effect on getting it to work unfortunately. My Macs still authenticate however.

[PiqueABoo]

backup Exec is not compatible, this may be a hotfix for 12.5 or even wait until the next release!

 

I've come to the conclusion that the name "BE for Windows Server" is a bit of a crock. Having lots of experience, I can't think of one version since 9 that was stable until it got to at least SP3.

 

I'm currently having fun with BE 12.5 on a 2008 (not R2).. this was released after Server 2008 and doesn't like it if you've got DFS-R replicating SYSVOL. There is no supported way to set replication back to FRS.

 

Could be I haven't done enough LiveUpdate and server reboot cycles[1] and it will eventualy work, but for now the only way to stop BE saying SYSVOL is corrupt is to stop the DFS-R service for the duration.

 

Windows Backup doesn't complain at all, but with that being so crippled now this is a fact that's not much help.

 

[1] You'd have thought it might pop up a dialog same way it used to after installing SPs, but I've seen BE LiveUpdates install things and quietly log a "needs a reboot" event. Thus I reckon you should always reboot after BE updates just-in-case.

[DMcCoy]

I'm currently having fun with BE 12.5 on a 2008 (not R2).. this was released after Server 2008 and doesn't like it if you've got DFS-R replicating SYSVOL. There is no supported way to set replication back to FRS.

 

Mine has been backing up the same setup with no issues. I've usually found that it works fine.

 

I've used lots of things in the past and they were all certainly worse.

 

Tapeware was ok, but a bit slow

Arcserve was bad on windows and shameful on Netware.

Retrospect was slow, glacially slow. With the stupidest ever media options I have ever seen.

BRU (for Mac). Was ok, although not updated nearly enough.

 

Windows Backup is actually pretty decent these days, I shall use it to dump backups onto the D2D server until BE supports R2.

[DrCheese]

Backup Exec 12.5 is unlikely to ever support R2, which is pretty crummy.

Backup Exec 12.5 on Server 2008 R2 RTM x64 errors | Symantec Connect

 

Currently, there are no plans to support Backup Exec 12.5 on WIndows 2008 R2. In future, they might release a hotfix for supporting remote backups of Windows 2008 R2.

[Kitkatninja]

We've upgraded to Windows 2008 R2 with relatively little hassle, we've also virtualised most of our servers. The only 2 problems that we've come across so far is problems with upgrading our DHCP server to 2008 r2, so we've left it as Windows 2003 (virtual, thank goodness for snapshots) and an initial problem with our Sophos Web Security & Control box, however that was a replication issue which has now been sorted.

 

-Ken

[PiqueABoo]

Mine has been backing up the same setup with no issues.

 

I'm sure it works for most folk, the trouble with BE is that sometimes it just doesn't (this is a fresh/clean/SP2 + fully patched OS install).

[ZeroHour]

Backup Exec 12.5 is unlikely to ever support R2, which is pretty crummy.

Backup Exec 12.5 on Server 2008 R2 RTM x64 errors | Symantec Connect

 

Thanks for that, but it is damn annoying....

We are just about to buy fresh BE lic's tomorrow and I was hoping this thread would lead to better news. Anyone heard of a eta of BE 2010?

[DMcCoy]

Listed in today/tomorrows updates is WSUS 3.0 SP2

 

Description of Software Update Services and Windows Server Update Services changes in content for 2009

[earlyriser]

Running 2008 R2 on a new DC and a few other servers, all going well so far but....

 

I upgraded my Windows Deployment Services server to R2 and at the time, remember reading something about it breaking Sysprep's ability to join XP machines to the domain , and lo and behold, Sysprep can no longer join an XP machine to the domain after being imaged using WDS! Haven't looked into it yet, but I suppose it's my own fault for not doing my research beforehand and leaping into R2.

 

Only other issue I have, which may or may not be R2 related is that in demoting our old 2000 DC to member server, and promoting the new 2008 R2 to be a DC (FSMO/DNS/DHCP etc.), something has become broken with my DNS Alias (CName) records in that I cannot browse to them anymore. I can ping them, and I can browse/map drives to the server shares themselves, but if I try to browse or map a drive to an alias, it fails.

 

Oh, and there is something about changes to authentication in R2 which has broken the ability to backup using Windows Server Backup directly to a NAS with ext2 drives.

 

Other than that, all good.......

[CaptainJack]

I upgraded my Windows Deployment Services server to R2 and at the time, remember reading something about it breaking Sysprep's ability to join XP machines to the domain , and lo and behold, Sysprep can no longer join an XP machine to the domain after being imaged using WDS! Haven't looked into it yet, but I suppose it's my own fault for not doing my research beforehand and leaping into R2.

 

Any word on a fix for this? We are beginning to make the move to 2k8 R2 and we will be using some XP boxes on this network for a while yet (mainly student computers, the bulk of our XP deployment) and I don't like surprises. At the least, thanks for this heads up!