Does anyone know if one way external trusts are allowed (SBS domain trusting another domain) in SBS R2 domains? I know this was not possible pre-R2, but with MS opening up the multi-site capability on R2, I was hoping they would lift this restriction as well.Windows 2003 R2 is geared more for branch offices . SBS 2003 r2 only has FSRM from the R2 bits. No, nothing has changed with trusts in the R2 era.
for a couple of years, it may be better, but from what I have read on several websites it is possible they may release another upgrade late 2007/early 2008, and to be honest I am surprised at their decision based on the numerous criticisms SBS has had over the years. Andrew.Numerous criticisms? RWW in 2k3 is hands down the killer app. Take the time to understand where SBS fits in your client base and it's a value to your business. Patching IS a big deal .. do you have a patch management process in place now?Jusg Google for SBS 2003 R2. go to some of the more rounded press. Most of my clients use VPN in and then use remote desktop without the web front-end, this also gives them access to download files onto their own machines for offline use etc. Yes, but not sure what
the "version upgrade" product, which means no "swing migration" is necessary. So, if you need the extra features, go for R2. Otherwise, it's not a "must have" upgrade. Pricing (and upgrade paths) for Windows Small Business Server 2003 R2 http://www.microsoft.com/windowsserver2003/sbs/howtobuy/pricing.mspx Windows Small Business Server 2003 R2: Powering Small Businesses http://www.microsoft.com/windowsserver2003/sbs/r2/default.mspx#3 Windows Small Business Server 2003 R2: Product Information (FAQs) http://www.microsoft.com/windowsserver2003/sbs/evaluation/faq/prodinfo.mspxHi Merv, We have 2 NICs; I think the problems was the service provider installer not Dell, I don't think thaty knew how to get the ISA working
and SMSMSE, no SQL other than SharePoint with very limited usage and Exchange of course which is highly used. Symantec BackupExec 10d is the backup software. I'd like to migrate them to a new server with SBS R2 using the swing migration. Can I do this with a clean R2 install off the bat on the new box or do I need to use the same version of SBS 2003 Standard then apply SP1, and then upgrade to R2 on the new box? Also, their Open Business License expired. Can I purchase SA to get them back on with licensing as well as entitlement to the R2 upgrade. They only have 5 users however I don't want to go thorugh a clean install, Exmerge, workstation migration, Any thoughts on this would be appreciated. AndrewTry here: http://www.sbsmigration.com/Thanks Frank. I know
Hi, Can i create DFS between Win2003 SBS R2 and Win2003 Std R2 ? JCAgain, I should have said that the assumption is that the Win2003 is a member of the domain just to clarify
I am installating SBS R2 - new installation on HP Prolian ML110 and have encountered the following error " you must be a member of domain admins schema admin or enterprise admin groups" I have install SBS support tools (from 2nd disc) and run dcdiag - which indicates the following error LDAP bind failed with error 1323", "unable to update the password". the value supplied as the current password is incorrect I also did the following from command prompt "netdom query fsmo" and received the following response "the specified domain does not exist or could not be contacted" when I tried from the mmc to transfer the Schema Master Role to the SBS server it would not allow indicating "logon failed". Thank you for any
$WSUS) database to another drive? 2) With install of WSUS I bellief all clients are updated to look at the load SBS server now. How can I check it was? ). But how can I add clients manually? 3) Did SBS R2 setup all clients to receive from SBS server for updates? 4) Missing really release notes on WSUS with SBS r@. Where is it? 5) Can I upgrade WSUS to V3 beta? Any linkd to manageing WSUS with SBS R2 would be appricated (especially related to SBS R2)Just wondering if with R2 WSUS, a GPO was automatically created to enable all computers to get updates? If so, under what name? This suppose to force the cleints to use WSUS intead of internet updates? Does SBS 2R WSUS force me to enable updates to bmade available as previous versions of WSUS?Are wireless systems included in the WSUS
segment. One hosts all my user accounts and the other is just an application server. My problems is the application server can only be accessed by its IP address rather than its FQDN. What do I have to do to DNS so my users can access the application server by name? CharlesYou only get one SBS server per domain. If you have an application server, then it should only be a member server and one built on Windows 2003 server (not SBS). Can you clarify what you really do have?I just so happens that both servers are SBS R2 servers each their own domain controller. CharlesFor name resolution purposes, you can zone forward each others domain to the other, or load each with the others zone as a secondary. Also, please cross post instead of mulit-postPlease clarify further. The 2
yet, so I want to look for another solution with MS technicians. The programs work fine and quick in the server, and it has the same antivirus but server edition. If we see differents between all system and the newest, only was change the new server installation, new domain and Windows SBS 2003 R2. Is there anything I should configure specially in this version?. The differences between old system and the new one, it was a new server installation, a new domain and Windows SBS 2003 R2. Is there anything I should configure specially in this version?. I have not configured domain directives yet. I followed best practices analyzer at the server and all is good. All the problems are in the XP computers after new domain join. Any ideas? I need help. Juan Carlos PD: Sorry for
I'm working on a site where the old network admin installed a 180 days trial of sbs sp1 and currently is running production right now. I want to get sbs r2 installed as easy as possible within the next week before the timebomb. Can sbs r2 setup be run over an sp1 eval version or will windows not allow this? Does anyone have any ideas besides installing r2 on a different box and migrating all information over to the box then install r2 on old box and migrating back because i don't want to go this route. thanks for your helpEvals should upgrade fine using Retail or Volume License versions. Not OEM versions. Upgrade *must* be done *before* the eval expires.
I know that the SBS R2 licensing allows us to use the R2 CALs for other Server 2003 servers in our organization. When we first went to SBS 2003, we were not a partner and purchased SBS 2003 Premium through volume licensing with SA. We are now at R2 and are going to add a Server 2003 box. We have an unused copy of Server 2003 through our Action Pack subscription but that has a limited number of CALs. Wondering if anyone knows if the SBS R2 CALs will work and if those SBS R2 CALs overrride the Action Pack Server 2003 CALs? TIA. JohnWhen you install that Windows 2003 server from the Action Pack and join it to the SBS domain using connectcomputer, the only cals that apply are the R2 cals Thank you. That's what I figured.
additional DC in our existing domain and would be a secondary Exchange server in case our primary was not reachable. Does anyone have any resources that would be helpful to us in planning for and configuring this scenario?You cannot have SBS as an additional domain controller for existing domain If you set up a SBS server in SanDiego as well it will be its own domain You would need to set up a regular Windows Server 2003 Server as an additional DC and you could set up an additional Exchange Server just not another SBS serverI was under the impression that SBS R2 would allow 2 SBS's in the same domain. I could swear that I had read this somewhere, but cannot find the article now. Is this incorrect?Yes, it's incorrect. Dyslexic perhaps. You can have two (or more) *email
I've used Ghost 2003 to upgrade hard disks, resize partitions, transfer to new hardware etc. over a Hundred times in the past With SBS R2 I had to Re-size partitions to create 3rd partition which will never be backed up (Admin tools) Found: Exchange won't start - had to set the DB to Allow Recovery. Started OK after I set DB to recovery SharePoint won't load - check connection error - haven't sorted this yet - need to spend more time on this Anyone see this behaviour ? big qestion is WHY??Check that your drive letters haven't changed. KathyThanks - checked that already!
I could tell you that there is only system data and folders on C. Those servers are prepared under Microsoft recomendations. Thats means that each application has its own partition on this server. The problem I have now is that the customer made click on updating boton and He accepted to update the system to SP2 without knowing that there is one partition for each application. I do not know anything about updating SBS 2003 R2 from SP1 to SP2. I think that there is a process to make it manually by downloading or copying the files on the work partition which is a partition for this kind of job only. This partition is empty normally. I am going to try to tell you the exact information for each partition but I can not make it right now because now it seems that the systm is updated
I have an existing SBS Prem 2003 machine, I need to update it to SBS R2. I contacted my software distributor who sent me the SBS R2 discs(looks like 3 disc of sbs, 1 for outlook, 1 for frontpage, 1 for entourage, and 1 prem technologies disc) which looks like a full set of discs, which confuses me a bit. Do i need to reinstall the OS to get R2? Or is there something i need to run from the discs?You have been supplied SBS Premium media, hopefully SP1 but _definitely not_ R2 SBS R2 has not yet been released.Yup we don't even know the SKU codes yet for R2.
We plan to deploy MS SBA 2007 as soon as it will be available for retail; in the meantime I am setting up a test machine where I would like to install SBS R2 and SBA Beta. My questions are the following: Is the R2 release available on MSDN the new one? I remember that there was one that was recalled. Do I need to download all the CDs or just "R2 Technologies" and "Premium technologies disk 1 and 2"? We bought SBS 2003 Premium and SA so we will receive R2, I just would like to test it before putting it in a production machine. Thanks in advance for your advice. StefanoYes, good bits. If SBS sp1 is already in place, all you need is the R2 cdroms/prem cdroms.
internal one bridged to the vm host only, same ip settings), the SQL 2005 upgrade went fine, but we're halted at the point of the R2 Technologies disc, "Install Windows Small Business Server 2003 R2". The error message is "Setup has encountered an error and cannot continue. Check the log file located at C:\Program Files\Microsoft Integration\Windows Small Business Server 2003\Logs\R2_Setup.log." The contents of that log are below. Prior to beginning our R2 upgrade, we moved our Sharepoint installation to a different server, and uninstalled it (and the MSDE database) from our SBS server. After suspecting it was that which was hanging us up, I reinstalled Sharepoint (through Add/Remove Programs>Windows Small Business Server, installing Intranet according
Hi All, I dont understand why but my SBS R2 Premium Edition server and all workstations underneath it have painfully slow internet speeds. I reran the internet connection wizard and checked Verizon DSL connecitity (which is blazing fast from any workstation outside the SBS network) and it is still painfully slow on the SBS network. Here is my ipconfig: C:\>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : server Primary Dns Suffix . . . . . . . : ostarenterprises.local Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : Yes DNS Suffix Search List. . . . . . : ostarenterprises.local Ethernet adapter Server Local Area Connection: Connection-specific DNS Suffix . :
be installed. If something isn't there, you have to install it before you can go to the next item. (SBS SP1 upgrade would be first on the list with its components broken out as well in order of installation, then Exchange SP2, then Sharepoint SP2, etc.) Each item you click on takes you to that installer. No need to hunt around to see what is already there. For most of us, we already know. For some, they have no idea, because they just let Windows/MS Update take care of things for them. Then, once all the Pre-requisites are completed, it installs the R2 technologies. Then, once that is complete, it offers you the optional stuff if you are on the Premium edition. And that is based on how SBS R2 is currently delivered, which I would change as well if I was in Bill G's shoes
should be a two stage process. Although the current upgrade is working fine from technical point of view, it is not appropriate from the license point of view. You may need to install the Windows SBS 2003 R2 Premium Technologies first (if you are installing the Premium Edition of Windows SBS 2003 R2). After that, please install the Premium Technologies on the SBS R2 server. For detailed information, you can contact the Microsoft license office that Russ mentioned on phone. Hope this helps. Miles Li Microsoft Online Partner Support Microsoft Global Technical Support Center Get Secure! - www.microsoft.com/security ===================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may
standard box I can add "win components" -> Active Directory-Services -> "Identitätsverwaltung für UNIX" on the sbs box I do not have this. Thought this was in "R2". how to get this feature for the sbs box ? Have I to install sfu35 ? And If I install sfu35, should I do this on both (sbs and std server) ? Any advice would be great. Kind Reagrds ChrisThe problem is that SBS R2 is NOT Server R2. Very confusing, I agree. SBS 2003 R2 is actually Server 2003 SP1 based, and none of the features in Server 2003 R2 are included in SBS R2 except FSRM. You can, however, use Services for UNIX version 3.5, which should still be available for download. Yes, here it is: http://www.microsoft.com/Downloads/details.aspx?familyid=896C9688-601B-44F1-81A4-02878FF11778
In attempting to join a client computer running windows XP media center edition SP-2 to SBS R2 I get the following error message from ConnectComputer: "an error occuried when configuring network settings. see your netwok administrator" and then the wizard quits However there is a way around it. Copied From Link https://msmvps.com/blogs/kwsupport/archive/2006/12/22/faster-banana-hack.aspx Faster Banana Hack Do you have a Windows Media Center Edition (MCE) PC you bought, but haven't been able to add it to your SBS domain. Until now, the Banana Hack was the only suggested way of doing it (without reformatting and reloading MCE from scratch). But, if you're like me, the Banana Hack, for whatever reasons, did not work. Kudos to James Barrett for posting a much
'd get pre-configured WSUS which would save you some time - and, if you get Premium - you'd the new SQL. But SQL versions (editions) have changed quite a bit with 2005 - you'd need to investigate. I understand the SQL site on MS.com has lots of information. It's my understanding many of the additions that are in Windows Server R2 are simply not applicable to an SBS network, and won't be implemented. So there may be very little (or no) reason for existing SBS 2k3 owners to upgrade at all.I haven't used SQL Server to date but will likely be taking some training in the first half of next year so using SQL Server 2005 is my only sensible option - I don't want to learn the new product and then have to relearn the old one. Ronnie
, I am doing this first in my lab, but will be doing it for a friends business in a few weeks. Being a Windows "expert", I figured of course I would just pop in the Windows SBS 2003 R2 CD and let it rip on a new install in a virtual environment. While it was installing, I would start to review the documentation. The documentation (http://www.microsoft.com/technet/prodtechnol/sbs/2003/support/documentation/58dab494-a46c-44db-9194-82581220e08e.mspx?mfr=true) says I need to have SBS 2003 SP1 installed before I can install SBS 2003 R2. Since my installation disk said SBS 2003 R2, I figured my install was going to fail. But here it is 45 minutes later and the install is still chugging along; happily it appears. Am I going to get a nasty surprise later, or has this requirement
domain. The "real" domain has a broadband connection with a dynamic IP address, an external combo router (wired & wireless), a single NIC configuration and DynDNS access. How can I simulate remote (i.e. Internet) access to this virtual SBS server so I can test various IIS settings related to RWW access and self-signed certificates on SBS R2? In other words how does the SBS server detect an incoming connection is from the Internet not an intranet connection? Doable?Hi Hugh, I think that if you want to test RWW access to an SBS box, virtual or otherwise, you could probably just point your browser to https://Internal_Servername/remote on either the server or your XP client Virtual System. I'm not sure what you're looking to test when you mention IIS
Hi, I have a new server I received from Dell with Win2003 SBS R2 Standard pre-installed. The server works great, however I can't seem to get the installed sharepoint to work. When I try to open any sharepoint page such as from the manage server snap-in, I get the message that it cannot connect to configuration database and that need to read article 823287 to resolve the problem. I read the article, but I can't seem to get sharepoint working. If I open a browser to the ip address of