Windows Server 2008 R2 Thread, 2008 R2 - Don't rush! in Technical; I have been trying to get Softlink Alice working on 2008R2, just to see if I can.
Apart from having ...
23rd August 2009, 03:32 PM #16
I have been trying to get Softlink Alice working on 2008R2, just to see if I can.
Apart from having to manually register the isapi extension and enable 32 bit app pool (Installer from 2003 for IIS5!) for the web inquiry, it all seems to work, even when run on the server rather than just as a file share!
I'm not sure if that says more about Alice seemingly to be fully 32 bit rather than 2008 being compatible with older applications.
Last edited by DMcCoy; 23rd August 2009 at 03:43 PM.
IDG Tech News
23rd August 2009, 09:54 PM #17
I came a cropper with 2 apps
WSUS and OCS 2007 R2
Both have had to be re-installed on non-R2 Servers...
Will prob shift WSUS back to its proper server if SP2 works!
24th August 2009, 09:50 AM #18
Smoothwall doesn't work with R2! At least NTLM doesn't.
24th August 2009, 01:41 PM #19
Mine working fine :S
Originally Posted by DMcCoy
I've pointed this thread to the good Sir Tom and I am sure he will be on to it like a bolt of lightening!
24th August 2009, 01:51 PM #20
NTLM ident works, NTLM auth does not. I can see the ldap requests, but the user is never logged in.
24th August 2009, 02:01 PM #21
Havent they changed NTLM for more security?
Originally Posted by DMcCoy
I read about the the other night, but the referencing docs arent up on technet at the mo.
24th August 2009, 02:41 PM #22
FYI, we're looking into this now for you Smoothie folks.
3 Thanks to rob_f:
DMcCoy (24th August 2009), john (24th August 2009), ZeroHour (24th August 2009)
24th August 2009, 04:43 PM #23
There is a beta out that allows SCCM 2007 to deploy r2/windows 7 but MS are saying if you install it you WONT be able to upgrade to release and will need to wipe but who knows if its actually blocked as an install.
Originally Posted by Crispin
24th August 2009, 09:44 PM #24
You need to do my S7000 fix on your R2 DCs, I will dig it out in a minute that will cure it I suspect, they have bought NTLM stuff right up to the latest top security and a LOT of kit isn't up to date with it as they are still using NT4 style NTLM which quite rightly in some cases is a bit sloppy as its very insecure now a days (so MS tell us) but should have been brought up to date. I don't know if this is what the Smoothy is struggling on, but I am sure Rob, Tom and crew will soon have it bossed
Originally Posted by DMcCoy
24th August 2009, 09:49 PM #25
Last edited by Theblacksheep; 24th August 2009 at 10:02 PM.
24th August 2009, 10:01 PM #26
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.
24th August 2009, 10:40 PM #27
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.
25th August 2009, 07:11 PM #28
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.
backup Exec is not compatible, this may be a hotfix for 12.5 or even wait until the next release!
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 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.
 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.
25th August 2009, 07:36 PM #29
Mine has been backing up the same setup with no issues. I've usually found that it works fine.
Originally Posted by PiqueABoo
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.
25th August 2009, 09:06 PM #30
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.
By Kamran7860 in forum Windows 7
Last Post: 5th May 2009, 03:17 PM
By Uraken in forum EduGeek Joomla 1.0 Package
Last Post: 5th December 2007, 02:03 PM
By edie209 in forum General Chat
Last Post: 10th November 2007, 03:39 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)