M_P_2
Level 2
Joined 18 years ago
User Profile
User Widgets
Contributions
Re: BE 12.5 - SBS 2008 Premium
Yes, We are unable to view resources, because Backup Exec failes to connect to the server. We have configured SBS2008 to use the Administrator account (instead of the SBS2008 admin account), configured all Services to use the Administrator account, changed all credentials in the BEUtility to use the administrator account, disabled the Windows firewall, but nothing works. Telnet to port 10000 works, so It's not a firewall issue. Every attempt with the Administrator account failed, so we used "Step 2" in one of the support documents: create a new account and make it member of ONLY Domain Admins and Administrators, where Domain Admins is Primary. We named this user Backupexec, changed all Services credentials to this user and used BEUtility to change en check the credentials again. Changed the default logon account in Backup Exec to the Backupexec user, rebooted the SBS2008 server... but still no luck. We have a number of 2008 Servers running as member servers without any problems (just install and runs like a charm), but we can't get SBS2008 to work... simply unable to connect and view resources. Of cource, we are testing with SBS2008 RTM, which is available for Microsoft Partners since September 2008.1.3KViews0likes0CommentsBackup Exec 12.5 SBS 2008
Excuse me, this post was supposed to be a reply to this thread: https://forums.symantec.com/syment/board/message?board.id=installations&message.id=1579 Yes, We are unable to view resources, because Backup Exec failes to connect to the server. We have configured SBS2008 to use the Administrator account (instead of the SBS2008 admin account), configured all Services to use the Administrator account, changed all credentials in the BEUtility to use the administrator account, disabled the Windows firewall, but nothing works. Telnet to port 10000 works, so It's not a firewall issue. Every attempt with the Administrator account failed, so we used "Step 2" in one of the support documents: create a new account and make it member of ONLY Domain Admins and Administrators, where Domain Admins is Primary. We named this user Backupexec, changed all Services credentials to this user and used BEUtility to change en check the credentials again. Changed the default logon account in Backup Exec to the Backupexec user, rebooted the SBS2008 server... but still no luck. We have a number of 2008 Servers running as member servers without any problems (just install and runs like a charm), but we can't get SBS2008 to work... simply unable to connect and view resources. Of cource, we are testing with SBS2008 RTM, which is available for Microsoft Partners since September 2008. Message Edited by M P on 11-13-2008 07:05 AMRe: IDR error "OS type was not determined from E:\I385\TXTSETUP.SIF"
E:\I385 ? ;) Anyway, MS created the slipstreamed SP1 Windows 2003 version in may 2005. It's Symantec's job to modify their software in order to work with a newer version, don't you think? To me, it seems like a simple OS recognision problem, because if the Windows version is English, IDR works like a charm with the SP1 integrated version of Windows 2003. Why it this so difficult for Symantec to solve? I think it's lazy. When running the IDR wizard, It first fails on recognizing the Windows CD. If we copy the complete Dutch Windows CD to the harddisk, and change the "cdname" and "productname" in the TXTSETUP.SIF file with the lines from the English TXTSETUP.SIF file, IDR will continue. So it's just a stupid recognision issue, right? We change "cdname" and "productname" from: "Windows Server 2003 voor Small Business Server" to "Windows Server 2003 for Small Business Server" (where the "cdname" line includes "CD-ROM") ...and the CD is recognized by the IDR wizard! It's too lazy. PS: you can find "cdname" and "productname" in the TXTSETUP.SIF file, starting at line 16076. The second problem sounds familiar: the OS is not being recognized by the Wizard. The problem is we don't know what the wizard is looking for. Strings in the registry? lines in a file? If we can fool this one, I think IDR is going to work for the Dutch version. Any ideas how the IDR Wizard determines the OS language? Thanks MP520Views0likes0Comments