out IP's and then I had a customer who had this happen today to them. Has anyone else had this happen? I know Chad did Roger Crawford HTSSo it's not the SBS 2003 SP1 + ISA 2004 problem that Chad Gross blogged?Well Les I didn't think so but I think I am wrong this is a fresh install SBS 2003 and then SP1 without having ISA 2000 on the box and installing ISA 2004 fresh. What I am seeing in my logs real time monitoring here at home is that the DHCP Request is being denied from Internal to local Host and the Destination IP is 255.255.255.255 and the Client IP is 0.0.0.0 and it denies the request. On my LAN I have 192.168.0.1 to 192.168.0.255 specified for the Internal Network. I did add a Rule that said allow this but it is still being blocked. Hmmm Roger
you apply this update, you must run the Configure E-mail and Internet Connection Wizard again after you apply the update. Then, you can publish your company's internal Web site to the Internet. Then, please try to install the SBS 2003 sp1 (KB885918) again. If we cannot resolve the issue after we perform the above steps, please kindly help me collect some information for further investigation: 1. Please send me the log C:\Program Files\Microsoft Integration\Windows Small Business Server 2003\logs\setup.log at [email protected]
2. Gather MPS report on SBS I suggest you download and run the MPS Report tool from the following link and then send the generated CAB file to my mailbox [email protected]
for further investigation so that we can find what the root cause
the NTDS folder or just the .log and .chk files. Many thanks for reading TonyAny help here Tony? "Directory Services cannot start" error message when you start your Windows-based or SBS-based domain controller http://support.microsoft.com/default.aspx?scid=kb;en-us;258062Hi Merv
Thanks for the post.
I have been through that and again but still no joy!
I was wondering if this would work, I appreciate that the email will
probably be lost but as Most are remote users then I can get them to
back up what they have locally.
1 Install SBS 2003 R2 on a different test machine
2 use the same domain name and server name
3 add users
4 Copy the NTDS Folder from the test to the problem server?
Any thought would be much appreciated
TonyAD is not a strong suit
Premium Edition. As a one-man accountant shop, I have no need of a separate server, so I've done nothing with it. Two days ago, while attending a continuing education expo, I had occasion to visit with the MS rep at the Microsoft booth. While discussing Small Business Accounting 2006, he happened to mention that I could install SBS 2003 Premium on my XP Pro machine and that the two OSs would coexist. In fact, I could logon to SBS 2003 from my XP desktop. And no, this is not a dual boot option--since in that case, I would be selecting one OS or the other, but not both. That night, I searched the Knowledgebase, as well as the docs that came with my software and found no reference to this coexisting installation. I went back for the second day of classes and asked the
have misunderstood your concerns, please do not hesitate to let me know. Before we install the SBS 2003 SP1 onto the server, we need to make sure that the required components such as Windows server 2003 SP1, Exchange 2003 SP1, WSS SP1 have been installed. Please refer to the release note and double check the install procedure: http://www.microsoft.com/downloads/details.aspx?FamilyId=022677CC-F5AC-4BFB- 9AD0-454E89CB98BB&displaylang=en Would you please help me confirm if you have strictly followed the document to install SBS SP1? For SBS 2003 Standard: http://download.microsoft.com/download/2/e/9/2e902d14-da2e-43ba-8bd6-6d258f5 356b6/SP1Setup_std.htm For SBS 2003 Premium: http://download.microsoft.com/download/2/e/9/2e902d14-da2e-43ba-8bd6-6d258f5 356b6/SP1Setup_prem.htm
work?Hello Customer, Thank you for kind update. If you had really download and install SBS 2003 sp1 on your SBS, please perform the following steps: If the system prompts you for SP1 installation CD3, follow these steps: a) Open Registry Editor and set 'isrunfromweb' to '2', under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer. b) Download SBS 2003 SP1 (KB885918) to C:\. c) Open CMD window and type "C:\SBS2003-KB885918-SP1-X86-ENU.EXE /x" (with no quotation marks) and press Enter. d) Specifying a path for the extracted files (such as C:\SBSSP1) e) Point the system to the folder created in the previous steps (C:\SBSSP1\CD3). If we cannot resolve the issue after we perform the above steps, please kindly help me collect
SBS 2003 SP1 removing servers from this environment into its own environment that is not associated with the SBS configuration and still allow for resources to be accessed. We have two companies configured on our LAN and want to seperate them into unique Forest or LAN Workgroup with individual ISP/Router/Firewall. First is a Operations with Exchange the second a Development using SMTP from the SBS Exchange with databases and sharing files and accessing files from the first. We want to design seperate network to assure individual security and ownership but yet have ability to share files/SMTP with the Operations side of business where the workstations will be designing from accessing a production environment. Thank you in advance AlCheck out the transition pack.If they have
installed the latest release of WSUS on an SBS 2003 SP1 Premium server. I did follow the MS KB for step by step guide to WSUS on SBS. My XP Pro SP2 clients are checking in correctly and getting their updates. My question is regarding the older clients like XP Pro SP1 or Win 2000 Pro SP4 clients. I have modified the IIS6 components for the SelfUpdate and ClientWebService to allow annonymous access and granted the security correctly. Also, I'm using the GP to send the AU files via http://sbs:8530. My question is that I cannot seem to browse any of these IIS directories via the client PCs and didn't know if this is a concern for future clients getting the latest AU files. For instance, if I try to open http://sbs:8530 or http://sbs/selfupdate from the internal clients
My understanding is that I cannot install SBS 2003 into an existing domain, and not have it assume a DC role. This is true, isn't it? My boss has given me a project plan which involves installing SBS 2003 into an existing domain, and then days later "promoting" it to a DC. That doesn't make sense to me. Thanks for any responses! JSee http://support.microsoft.com/kb/884453/en-us paying particular attention to the hard and fast restrictions.Also if it doesn't make any sense to you perhaps you need to hire an SBS specialist to do the job-you may not have enough knowledge or experience to do it yourself.Sorry re-reading your post I think I misinterpreted what didn't make sense to you. When a new SBS is joined into an existing domain using the reference
CDs. Is the reason that I am getting this error message that I am trying to install SBS 2003 Standard Edition SP1 which is what Microsoft has on their website? When I try to do this I get a setup error message 885918. Is this the error message that one gets when they try to upgrade SBS 2003 Premium Edition with the SBS 2003 Standard Edition SP1 or is this another issue? Rick Bellefond RB Data ServicesAnother reason. All of us use the Standard SP1 even if we are premium. http://support.microsoft.com/default.aspx?scid=gp;[ln];kberror&style=error what is kb 885918 as I don't see it on the web?Susan, That is good to know that you can apply a SBS 2003 Standard Edition sp1 to SBS 2003 Premium Edition. If you Google kb885918 a number of things turn up but none of
hungry". I've got 4 client sites running just fine on P4 2.8 GHz Dell servers (1 GB RAM for SBS Standard, 2 GB RAM for SBS Premium); number of users ranges from 5-45. Plan on installing at least 3 times: the first to see what's it's all about; the second time to take notes and see what your options are; the third time to finalize your notes and the installtion. When you're dealing with a complex set of integrated applications, there's always a learning curve. Do yourself a favor and use the Wizards as much as possible. They're there for a reason. If you don't want to dive into SBS 2003 SP1 (recently released), don't install it until later. You've got some good online resources available to
Hello, We have Windows 2003 Server Enterprise Edition Installed on a server it is becoming a pain securing it with ISA, get the SMTP Services to work We are wondering if it is possible to install SBS 2003 SP1 Premium Edition on top of Windows 2003 Enterprise Edition? Thank you for your help?No. For one thing, you may have an incompatible domain infrastructure. Andrew.Thanks Andrew.
We have upgraded SBS 2000 (with ISA 2000 server) to SBS 2003. I'd like to be sure to have all Service Packs installed and, because of their relationship with the different versions of SBS: do I have to consider my SBS 2003 as a "Premium" version (we ha ve ISA 2000, not 2004)? and finally, how to look for the SP already installed?If you have the "premium" version that you want to get SBS 2003 sp1 on media so you can install [and get] the ISA 2004. Go to the website and order the SP1 cdroms.Hi Omar, Thanks for your post. To view the version of SBS, you can run "Explorer" on the SBS server to open the explorer, then, in the menu of the explorer window, click Help -> About windows. You will be about to see the detail information
HI All, We have two Dell poweredge servers. An SBS 2003, and a Server 2003 standard (TS in app mode). I have to apply SBS 2003 SP1, and Exchange 2003 SP2 to our SBS 2003 server, and Windows 2003 Server SP1 to our Windows 2003 standard server. I've read the SP1 article on smallbizserver.net but it doesn't mention Exchange SP2? Is that pretty straight forward to do after the SP1 install? Is there a prefered order for applying SP1 to the TS server? MarkHi Mark, You can apply Exchange SP2 in place of Exchange SP1, there's no need to do Exchange SP1 first. You can install Exchange SP2 before SBS SP1, or at the same time. The terminal server can be updated independently of the SBS - before or after the SBS - it makes no difference.Worked a treat.. except no-one told
I have been fighting with my server for the last two days. (It kicking my tail:>) I am trying to intall Sbs 2003 SP1. It fails at the Administration Componet, Intranet Componet, MSDE 2000 Service Pack 4. Has anyone come across the problem. And I would like to do a reinstall of SBS 2003. What are the steps to preserve the data. Bryan KrossleyI ran across a similar problem awhile back. This site helped me considerably and I have successfully installed SP1 11 times now under a variety of different setups. http://www.smallbizserver.net/Default.aspx?tabid=236 The following excerpt may point to the root of your problem. Make sure you are logged in as the build in Administrator before you try to install SBS SP1. Even an user with full admin rights, won't be able to
If I am off-base, please don¡¯t hesitate to let me know. First of all, Exchange is a fundamental component of SBS, many tasks and wizards are tightly integrated with Exchange, it¡¯s not commanded to install SBS 2003 without Exchange. When you applied SBS 2003 R2, the installation also applied Exchange SP2, since you don¡¯t have Exchange, something unexpected may happened. Based on current situation, the problem may be more complex and time consuming. Thanks for your understanding. When you running the Add/Remove Program files to change the components of SBS, the help file shows that the action may change computer name and AD setting. In fact, we cannot reproduce your situation to make sure the process will finish successfully if continue the wizard. At this point, please first
Hello people, I realise this is a pretty stupid question, but I just don't seem to find the answer ! I'd like to install SBS 2003 from scratch on a Virtual PC 2004 to test a couple of things. In general, when I want to do this, I "make" a new PC in Virtual server, start it, put in the XP or 2003 CD and launch the setup. However, in this case, the SBS 2003 CD does not seem to boot. I don't think there is a problem with the CD, so I am probably missing something here. Can somebody point me in the right direction ? Thanks a lot ! Benoit.See my reply in the SBS 4.5 newsgroup.
rights.File sent - see mail from Gary HunterDear John, Thank you for your update. I had checked the log files that you had provided. The log files did have indicated that you had installed the SBS 2003 SP1 on the computer correctly. (no problems found in the log) Based on the following situation, let us try the following steps to check the issue again: 1. Disable all the third party applications on the computer. (Especially the Anti-virus application and firewall applications) 2. Backup and delete the log files in the "C:\Program Files\Microsoft Integration\Windows Small Business 2003\logs\" folder. 3. Then reinstall the SP1 on the computer. 4. If the error message appearred again, please capture a shapshot and send it to me. 5. Send me the event log files and the
We're about to migrate a SBS 2003 SP1 to a new OEM SBS 2003 R2 box. Is it ok to use the ADMT (Active Directory Migration Tool) and procedure as mentioned in this white paper? http://www.microsoft.com/technet/prodtechnol/sbs/2003/deploy/sbs2k203.mspx Does anyone know of any other useful documents or guides to complete the migration? Thankyou for your help, Jonathanwww.sbsmigration.com
Hi, A collegue of mine installed SBS 2003 on a new server. After that he installed windows server 2003 SP2 on this machine. Is this possible? We have no R2 version. After the install of SP2 he did an install of SBS 2003 SP1 on the same machine. This update goes wrong. We also can't install SQL SP1. So I think the install order is wrong!. Can anyone help me. Thx in advance, Ramonyou can install sp2 on SBS R2 as it says sp2 downloads instructions . http://www.microsoft.com/downloads/details.aspx?FamilyID=95ac1610-c232-4644-b828-c55eec605d55&DisplayLang=en "Windows Server 2003 Service Pack 2 (32-bit x86)" you should uninstal sp2 instead of installing sp1 over sp2 anyway in certain circumstances you have to uninstall sp2 to do some tasks: http://
and reinstall the client apps folder.Hi Owen Williams, Thanks for posting here. without installing Outlook 2003 during the SBS 2003 setup, and now you failed to install SBS 2003 SP1. If I off the base, please don't hesitate to let me know. This is a known problem when Outlook 2003 is not installed during the SBS 2003 setup. This is a requirement to install SBS 2003 SP1. You need uninstall your Office 2003 applications, then re-run the SBS 2003 setup and choose to install Outlook 2003 in the ClientApps folder and then install SBS 2003 SP1. And you still can install office 2003 to another folder after you install Outlook 2003. Additional information about SBS 2003 SP1: http://support.microsoft.com/default.aspx?scid=kb;en-us;842690 Hope this helps. If you have any further
Hi, I'm running SBS 2003 SP1, Exchange SP2 and I'm using a Treo 700W with the messaging/security feature pack. When I try to sync, I get the "Your account in MS Exchange Server does not have permissions to sync with your current settings. Error code: 0x85010004." I've gone through the documents listed in other posts to verify settings on the exchange-oma directory (and they appear correct) and to make sure the ESM -> Global Settings -> Mobile settings don't require a pw. I am using a 3rd party cert and I don't receive any errors when accessing https://mail.mydomain.com/oma from the handheld or from my computer. I have tried syncing both with and without SSL with the same problem. What else could be causing the drama? Thanks! StuI had
As suggested by Merv Porter in another thread, I decided to try to reapply SBS 2003 SP1 (SBS2003-KB885918-SP1-X86-ENU.EXE) on the server. It was originally installed using SP1 media, and I have not specifically installed any service packs since. Unfortunately the installation fails with this message: Windows Small Business Server Service Pack 1 Setup has encountered an error. For more information, review the most recent entry in the Setup error log in C:\Program Files\Microsoft Integration\Windows Small Business Server 2003\logs\setup.log. Then correct the error and run Service Pack 1 Setup again. The setup subsequently finishes and offers to restart the server. Here is the most recent entry in the Setup error log: Component Name: Microsoft Search Version: 2.0 Installation
installation guide for the server to the point it is ready to install an operating system. I identified the OS to be installed as server 2003 and put SBS 2003, disk 1 in the CD drive. An error message says it cannot find the necessary files. How do I proceed from here? It has occurred to be to exit the installation guide and start the SBS setup. Will that work given that the server has no operating system at this point? HurleyTo Dick, It's seems to me that you've bought Win SBS 2003 OEM version (it came with only 3 CDs), correct? Is it the Standard Edition or the Premium Edition? There are more steps to follow if you're installing the Premium Edition not to mention if you have the Win SBS 2003 SP1 CDs. How about the IBM xSeries, which one do you bought
check http://support.microsoft.com for regional support phone numbers. Any input or comments in this thread are highly appreciated. ===================================================== This posting is provided "AS IS" with no warranties, and confers no rights. -------------------- <Thread-Topic: Install Exchange 2003 SP1 on SBS 2003 server <thread-index: AcfZit4nX0uZSwr4Svu8viub4Zf+sQ== <X-WBNR-Posting-Host: 188.8.131.52 <Subject: Re: Install Exchange 2003 SP1 on SBS 2003 server <Lines: 29 <MIME-Version: 1.0 <Content-Type: text/plain; < charset="Utf-8" <Content-Transfer-Encoding: 7bit <X-Newsreader: Microsoft CDO for Windows 2000 <Content-Class: urn:content-classes
not be "installed" on the server but if you go to the clientapps folder on the server, is Outlook 2003 there? (to be installed on workstations??)within the client apps on the c:\ drive, office2003.msi is present however, we moved this on to a d:\ partition before running the service pack.would this make a difference? If so can it be removedYes, you have to modify the registry if it still has the old path.Could you please let me know which registry i need to make the changes too, or how i can remove outlook completely from this scenario. if this is what is causing my SBS 2003 SP1 install to fail. It needs to be resolved urgently as i have almost no hair on my head to tear outThanks, any idea how i can install outlook 2003 in the clientapps as suggested. I did not