Server SBS 2003

How do I get a folder that is on the server to be sync to the workstations desktop when they login?

This one may help.
http://technet.microsoft.com/library/cc785925.aspx
Might also ask them over here.
http://social.technet.microsoft.com/Forums/en-US/home?forum=smallbusinessserver
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Similar Messages

Can´t install KB961143 on Spanish language server SBS 2003 SP2

We need to apply this KB961143, we found
Hotfix SBS2003SP1-KB961143-X86-ENU.EXE but is doesn´t work with our server
2003 SBS SP2 - Spanish-
Thanks.

Hi LCSMAR,
Based on your description, it’s hard to narrow down the root cause. Would you please let me know the complete
error message that you can get when fail to install this Hotfix?
In addition, please check if .NET Framework 2.0 installed before you apply this Hotfix.
Meanwhile, please check if you have installed
KB2028492. If not, please install KB2028492, then download the Hotfix
here manually and check if you can install it successfully.
If this issue still persists, please refer to the following article to reset Windows Update components and
monitor the result.
How do I reset Windows Update components?
By the way, please check Event Viewer and log file if you can find some relevant errors. Those may help us
to go further.
Hope this helps.
Best regards,
Justin Gu

Problems in connecting to Windows SBS 2003 server from OSX 10.5.x

Hi there
Out of many Macs (all 10.5.4) in our network, I have been able to authenticate others to the Active Directory and share File services of the Windows Small Business Server (SBS) 2003. But one is having problems. They have authenticated to the active directory correctly from Directory utility.
But when I try to access the SBS server, there is a message "Connecting to smb://myserver..." displayed for indefinite time. Also, I don't find the smb listed in Directory utility. Is that a problem? If so, how can it be fixed? I searched Internet but couldn't find a way to download smb client.
Please help.

It certainly works for me although I have 10.5.2. No special settings, just server address, username and password and it connects. To confirm I just tried it once more a moment ago by creating a new VPN configuration. No problems at all. Is your problem related to a single computer or is it so that now 10.5 computers can connect?

Active Directory not replicating from SBS 2003 to Server 2008 R2 Standard

I have an old SBS 2003 server and am migrating to a 2008 R2 server. I followed this guide:
http://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/
I followed the guide (except the exchange stuff, because they are moving from exchange to Google apps for business) and everything went fine.
I removed the sbs from Domain controller status (dcpromo'ed it out) and everything seemed to go fine. I haven't turned off the old server yet, because they are still using it for a couple of other unrelated applications.
After I did this I added new computers to active directory, but they only showed up on the active directory on the old sbs (I think something went wrong when I too the old sbs out of domain controller status).
I ran dcdiag on the new server and this is the result:
  Time Generated: 01/10/2014   14:57:56
            Event String:
            The SiSRaid4 service failed to start due to the following error:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:57:56
            Event String:
            The stexstor service failed to start due to the following error:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:57:56
            Event String:
            The vhdmp service failed to start due to the following error:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:57:56
            Event String:
            The vsmraid service failed to start due to the following error:
         A warning event occurred. EventID: 0x8000001D
            Time Generated: 01/10/2014   14:58:00
            Event String:
            The Key Distribution Center (KDC) cannot find a suitable certificate
to use for smart card logons, or the KDC certificate could not be verified. Sma
rt card logon may not function correctly if this problem is not resolved. To cor
rect this problem, either verify the existing KDC certificate using certutil.exe
or enroll for a new KDC certificate.
         An error event occurred. EventID: 0x0000164A
            Time Generated: 01/10/2014   14:58:20
            Event String:
            The Netlogon service could not create server share C:\Windows\SYSVOL
\sysvol\PIIKANIPW.local\SCRIPTS. The following error occurred:
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 01/10/2014   14:58:21
            Event String:
            The Qntm3520 service failed to start due to the following error:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   14:58:36
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         A warning event occurred. EventID: 0x00002724
            Time Generated: 01/10/2014   14:58:40
            Event String:
            This computer has at least one dynamically assigned IPv6 address.For
reliable DHCPv6 server operation, you should use only static IPv6 addresses.
         A warning event occurred. EventID: 0x800013B8
            Time Generated: 01/10/2014   14:58:49
            Event String:
            The application '/tmsWebAgent' belonging to site '1' has an invalid
AppPoolId 'Classic .NET AppPool' set. Therefore, the application will be ignore
d.
         A warning event occurred. EventID: 0x80003BC4
            Time Generated: 01/10/2014   15:01:53
            Event String:
            SSL Certificate Settings deleted for Port : 0.0.0.0:50106 .
         A warning event occurred. EventID: 0x80003BC5
            Time Generated: 01/10/2014   15:01:53
            Event String:
            SSL Certificate Settings created by an admin process for Port : 0.0.
0.0:50106 .
         An error event occurred. EventID: 0xC0001B7A
            Time Generated: 01/10/2014   15:01:59
            Event String:
            The TMS Print Agent service terminated unexpectedly. It has done th
is 1 time(s).
         A warning event occurred. EventID: 0x0000000C
            Time Generated: 01/10/2014   15:02:00
            Event String:
            Time Provider NtpClient: This machine is configured to use the domai
n hierarchy to determine its time source, but it is the AD PDC emulator for the
domain at the root of the forest, so there is no machine above it in the domain
hierarchy to use as a time source. It is recommended that you either configure a
reliable time service in the root domain, or manually configure the AD PDC to s
ynchronize with an external time source. Otherwise, this machine will function a
s the authoritative time source in the domain hierarchy. If an external time sou
rce is not configured or used for this computer, you may choose to disable the N
tpClient.
         An error event occurred. EventID: 0x0000165B
            Time Generated: 01/10/2014   15:02:34
            Event String:
            The session setup from computer 'PK-PC1' failed because the se
curity database does not contain a trust account 'PK-PC1$' referenced by t
he specified computer.
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:03:37
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         A warning event occurred. EventID: 0x000727AA
            Time Generated: 01/10/2014   15:04:01
            Event String:
            The WinRM service failed to create the following SPNs: WSMAN/PKDC01.
PIIKANIPW.local; WSMAN/PKDC01.
         A warning event occurred. EventID: 0x80003BC4
            Time Generated: 01/10/2014   15:06:54
            Event String:
            SSL Certificate Settings deleted for Port : 0.0.0.0:50106 .
         A warning event occurred. EventID: 0x80003BC5
            Time Generated: 01/10/2014   15:06:54
            Event String:
            SSL Certificate Settings created by an admin process for Port : 0.0.
0.0:50106 .
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:08:37
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x000016AD
            Time Generated: 01/10/2014   15:13:21
            Event String:
            The session setup from the computer PK-PC1 failed to authentic
ate. The following error occurred:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:13:38
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:18:39
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:20:28
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000457
            Time Generated: 01/10/2014   15:20:33
            Event String:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:23:39
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:28:40
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:33:41
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved. This issue may be
transient and could be caused by one or more of the following:
         An error event occurred. EventID: 0x00000422
            Time Generated: 01/10/2014   15:38:41
            Event String:
            The processing of Group Policy failed. Windows attempted to read the
file \\PIIKANIPW.local\sysvol\PIIKANIPW.local\Policies\{31B2F340-016D-11D2-945F
-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Po
licy settings may not be applied until this event is resolved.
         ......................... PKDC01 failed test SystemLog
      Starting test: VerifyReferences
         ......................... PKDC01 passed test VerifyReferences
   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test
         CrossRefValidation
   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test
         CrossRefValidation
   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
   Running partition tests on : PIIKANIPW
      Starting test: CheckSDRefDom
         ......................... PIIKANIPW passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... PIIKANIPW passed test CrossRefValidation
   Running enterprise tests on : PIIKANIPW.local
      Starting test: LocatorCheck
         ......................... PIIKANIPW.local passed test LocatorCheck
      Starting test: Intersite
         ......................... PIIKANIPW.local passed test Intersite
I also noticed that the SYSvol share on the new server is empty and the NETLOGON share doesn't exist.
Please help! Thanks.

Hi,
Do you currently have any relevant errors in your System or Application logs?
Seems like the replication is not successfully.
An SBS server shouldn't shut down upon detecting the existence of another DC as that's a fully supported scenario.
Regards.
Vivian Wang

Windows SBS 2003 to Server 2012 Essentials R2

I am tasked with upgrading from an existing SBS 2003 server to 2012 R2 Essentials. Currently the 2012 box is on the network, fresh install but I'm encountering issues from there. I joined it to the domain and now when it boots up it goes through the process
of configuring it to the domain. However, it simply stops with the error "Configuration Encountered Some Issues". Could someone provide some guidance? Thanks!
The only error I can find related to it is:
Log Name: Microsoft-Windows-ServerEssentials-Deployment/Deploy
Source: Microsoft-Windows-ServerEssentials-Deployment
Date: 2/8/2015 10:34:21 PM
Event ID: 130
Task Category: None
Level: Error
Keywords:
User: SNL\halo
Computer: Server2012.snl.local
Description:
Unexpected error occured: System.Management.Automation.CmdletInvocationException: Value cannot be null.
Parameter name: container ---> System.ArgumentNullException: Value cannot be null.
Parameter name: container
at Microsoft.WindowsServer.Essentials.ActiveDirectory.DirectoryEntryExtensions.GetNewChildName(DirectoryEntry container, String preferredName)
at Microsoft.WindowsServer.Essentials.ActiveDirectory.WellKnownStandaloneMsa.Initialize(Domain domain, DirectoryEntry master, Guid wkguid, String preferredName, DirectoryEntry& entry, String& connectedServer)
at Microsoft.WindowsServer.Essentials.ServerSetup.ServerSetupMsaHelper.InitializeServiceAccount()
at Microsoft.WindowsServer.Essentials.ServerSetup.ServerSetupMsaHelper.UseServiceAccount(NetworkCredential credential)
at Microsoft.WindowsServerSolutions.Setup.Commands.InitialConfigurationHelper.StartInitialConfiguration(PSCredential credential, Dictionary`2 data)
at Microsoft.WindowsServerSolutions.Setup.Commands.InvokeEssentialsConfigureServiceCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Windows.ServerManager.ServerEssentials.Plugin.RemotePSHelper.InvokeRoleConfigurationCommand(String command, IDictionary`2 parameters, Func`1 isCancellationRequested, Action`1 onProgress)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-ServerEssentials-Deployment" Guid="{AD9FC988-EB6F-43AF-9429-7BCDB78A7663}" />
<EventID>130</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-02-09T03:34:21.429892000Z" />
<EventRecordID>180</EventRecordID>
<Correlation ActivityID="{E85BC2B0-4415-0000-D0C2-5BE81544D001}" />
<Execution ProcessID="3140" ThreadID="2628" />
<Channel>Microsoft-Windows-ServerEssentials-Deployment/Deploy</Channel>
<Computer>Server2012.snl.local</Computer>
<Security UserID="S-1-5-21-3716708206-3900771979-3496404321-1138" />
</System>
<EventData>
<Data Name="Message">System.Management.Automation.CmdletInvocationException: Value cannot be null.
Parameter name: container ---> System.ArgumentNullException: Value cannot be null.
Parameter name: container
at Microsoft.WindowsServer.Essentials.ActiveDirectory.DirectoryEntryExtensions.GetNewChildName(DirectoryEntry container, String preferredName)
at Microsoft.WindowsServer.Essentials.ActiveDirectory.WellKnownStandaloneMsa.Initialize(Domain domain, DirectoryEntry master, Guid wkguid, String preferredName, DirectoryEntry& entry, String& connectedServer)
at Microsoft.WindowsServer.Essentials.ServerSetup.ServerSetupMsaHelper.InitializeServiceAccount()
at Microsoft.WindowsServer.Essentials.ServerSetup.ServerSetupMsaHelper.UseServiceAccount(NetworkCredential credential)
at Microsoft.WindowsServerSolutions.Setup.Commands.InitialConfigurationHelper.StartInitialConfiguration(PSCredential credential, Dictionary`2 data)
at Microsoft.WindowsServerSolutions.Setup.Commands.InvokeEssentialsConfigureServiceCommand.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at System.Management.Automation.PowerShell.EndInvoke(IAsyncResult asyncResult)
at Microsoft.Windows.ServerManager.ServerEssentials.Plugin.RemotePSHelper.InvokeRoleConfigurationCommand(String command, IDictionary`2 parameters, Func`1 isCancellationRequested, Action`1 onProgress)</Data>
</EventData>
</Event>

Hi Kieran S,
As Robert mentioned, did you refer to any migration guide?
Migrate from Previous Versions to Windows Server 2012 R2 Essentials or Windows Server Essentials Experience
Windows Server 2012 R2 Essentials Migration – Keys to Success
-->it simply stops with the error "Configuration Encountered Some Issues".
Please refer to Paul's suggestion and check if help you to solve this configuration issue. In addition, you can also refer to following KB.
The Post-Deployment Configuration task may fail after you install the Windows Server Essentials Experience role on Windows Server 2012 R2
If any update, please feel free to let us know.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Those two links were very helpful! Way better than the one I was referencing. I ended up having to manually do a adprep /forestprep before the wizard would work. All is well now, thanks!

Does SBS 2003 need M$SQL Server?

Hi All,
I have just picked up a new customer with SBS2003. (I can not tell if it is R1 or R2.) He is using it primarily as an Exchange Server and to share files with Quick Books. The server has M$SQL 2005 installed on it. The server is "refurbished".
His backup is horrible and he does use RAID.
The original consultant has moved to another state. For backup proposes, I inquired of him as to why he had M$SQL installed. This came back from him:
"Exchange does not use SQL. however, SQL is a core service in Windows Small Business Server (SBS). It holds databases for sharepoint and performance metrics for components of SBS. It's a major piece and SBS would be unstable without
it. "
Huh?
"Sharepoint" is a web development tool. Is it even part of SBS 2003?
What "Performance metrics"?
Since when is SBS2003 "unstable" without any SQL server installed?
Am I missing something? 2005 sql server only came with the more expensive version of R2. If this is R1, M$SQL 2005 was not invented yet!
Anyway, I'd appreciate an education here.
Many thanks, -T

You can still order SBS 2011 from legit sources on the web and rumor has it from HP. But you don't have to purchase the hardware at the same time as the software. I don't think the sky will fall in April, but it is definitely time to move on in a planned
way. I see SBS 2011 for less than 1K USD on the net. Compare that to replacing with standard Exchange and Server at a cost of 4K and up.
SBS 2011 will be supported until 2020 giving you and your customer time to plan for the next round.
Alternatives are Server 2012 Essentials (Role or SKU) and hosted email.
Hi Larry,
His current system works. He sees no economic justification to upgrade to a slower, buggier, more complicated server. He also can not afford it. If his current "refurbished" server dies, it would be better to put him on Zoho mail
at about $30.00 per month. If he still wants his own hardware, Zimbra or Open Change on Scientific Linux / Cent OS would be only the cost of the hardware and the set up fee. It would give him a lot more stability and software that can be easily
upgraded. If he really wants to stay with Windows Server, I do like your sbs2011 idea. Better all around if he goes with Zoho or gMail. (I am surprised he hasn't been eaten alive with spam.) Thank you!
-T

If you were going to use an XServe as a (gulp) SBS 2003 Server

would you keep an OSX partiion??
I'd LOVE to get rid of my Dell box, which handles my accounting and security. My idea is to get an XServe (smaller rack presense, easier to maintain, etc) and install SBS 2003 on it, then "sell the Dell". My cabinet would look a LOT better with NO DELL boxes.
I'm thinking about only one partition for Windowze so I don't have to administrate another OSX station (that can only be accessed with a re-start anyway).
My plan would be to burn the BootCamp drivers first, start-up from the Windowze CD, erase the OSX drive, format the drive and install a fresh SBS 2003. Then install the BootCamp drivers...
Any reason this shouldn't work??
MacPro 3gig Mac OS X (10.4.9)

Certainly a trail blazer
So a couple important things to note about the whole Boot Camp thing:
1) If it works and you can boot to Windows 2003 server, still, there may be devices that do not work because there will be no drivers for the embedded hardware. Some work on your part.
2) If somehow this should become supported, note Boot Camp is beta software and drivers will not ever be final for Tiger. To get the "final" drivers you'd need to upgrade to Leopard.
I'd be interested to hear how your experience goes. I admire your dedication to using the wonderful Apple hardware but you're going out a bit on a support limb. Actually there's no limb at all.. you're more like a pole climber at a lumberjack competition

Windows sbs 2003 sp1, windows server 2008 R2

I have windows sbs2003 sp1 & windows 2008 R2 Licenses...I want to setup ERP application with SQL on windows 2008 R2, Terminal server windows 2008 R2 for RDP & Ncomputing & E-mail server for Internal and external use. I have IBM Server with
XEON processor and 24 GB RAM.
I am using VMware ESXI 5.5 for virtulisation and installed one instance of WINDOWS SBS 2003 with Exchange for DC & EMAIL...and 2008 R2 one instance as member server for Application server ( ERP with SQL Express ) and another instance with Terminal server
and other application.
Above set up is not working smooth as it was expected..some times DC fails and so Exchange...Can you suggest any better alternative or correct method of implementation.

Hi
You should separate Exchange and DC on the same server and introduce a second DC incase the first one goes down.
Perhaps install Exchange on server 2008 r2.

SBS 2003 to Server 2008/Exchange 2007

We are in the process of moving our location and are in need of moving
from SBS to something with more CALs. I want to make this as seemless
as possible for the end-users.
We are currently on SBS 2003.
My plan:
Purchase new 64 bit server with Server 2008 and Exchange 2007.
Add new server to existing domain.
Move/migrate exchange from SBS to new server.
Make sure the user info and and Group profiles move to the new server
(not sure how to do that)
Remove the SBS, and promote the new 2008 to DC.
Possibly rename the 2008 to the same name and IP as the old SBS (so
outlook users do not have to change anything)
Would that be the correct route? If so, what am I missing? (Looks
easy on paper)
Thanks,
Mike

hi
here is a lead
Start by installing Windows Server 2008 on the server you’re intending on using for mail. In our example we installed all the Exchange functionality on a single server – in practice you’ll probably want to separate out the Hub and Storage
functions, and use a separate Edge server for mail traffic and user access to mail. There’s no problem with connecting to the network while you’re doing the install – Windows Server 2008 installs as a workgroup server – and you’ll
automatically be delivered the latest drivers and the most up to date OS patches. You’ll also need to give the server an appropriate fixed IP address, as it’s going to become a key component of the network infrastructure.on the role and feature-based
install model introduced with Windows Server 2003 and enhanced in Windows Server 2003 R2. Make sure you use these tools to install Internet Information Server – as Exchange 2007 will use it for Outlook Web Access and Exchange ActiveSync. Exchange 2007
requires that servers have the PowerShell management scripting environment and the
.NET framework. We’d also recommend installing Terminal Services as part of any Windows Server installation, as using Remote Desktop to access the new server and the existing SBS 2003 domain controller will let you handle much of the
migration process from the comfort of your desk.Once Windows Server 2008 has been installed, take out the install DVD and shut the server down. As you’re going to be adding a Windows Server 2008 machine to what’s really a Windows Server 2003 network,
you need to upgrade the Active Directory schema on our SBS 2003 server. This will allow you to manage the Windows Server 2008 machine from the SBS 2003 machine. You may need to update your version of Remote Desktop to one that supports the latest versions
of the RDP protocol.Put the Windows Server 2008 DVD in your SBS 2003 machine’s DVD drive (a network accessible DVD drive is suitable, especially if access to any machine room is limited, and you’re using Remote Desktop to manage
the server). Open a command line and change directory to SOURCES\ADPREP. You need to use ADPREP.EXE to update the Active Directory schema. Start by typing the following command to update the Active Directory forest.adprep.exe /forestprep.This will
begin the process of updating the schema. Be prepared to wait some time, especially if you’re working with SBS 2003 rather than SBS 2003 R2. Once the forest schema has been updated you can update the domain schema. Type the following command:adprep.exe
/domainprep.You’re now ready to bring the new Windows Server 2008 machine into your existing domain. Turn on the server, and then log in as a local administrator. Again, you can use Remote Desktop to work with the server, so you don’t need
to sit in the machine room.to the existing SBS-managed domain. Once the server is part of the domain, you will to promote it from a member server to a domain controller. Launch DCPROMO
using the Start menu search bar to find the program. Choose to add a domain controller to an existing domain. You’ll need to use the credentials of an existing domain administrator to start the process.Make the server a Global Catalog server.
If you’re going to be keeping the existing SBS 2003 system there’s no need to make the new server a DNS server. DCPROMO will then add the requisite Active Directory Domain Services to your Windows Server 2008 machine. This can take some time, especially
if you’re working with a large SBS-managed network with more than 50 users. Once the DCPROMO process is complete you’ll need to restart the server. You can now log in as a domain administrator.Now you can start the process of installing Exchange
2007 on the new server. There’s one key issue that needs to be dealt with first. Exchange 2007 needs to install on a server that’s a Schema Master.
One of the limitations of SBS 2003 is that the SBS server needs to own all five of the FSMO
roles. The Flexible Single Master Operations are key domain management tasks, and in a standard Active Directory implementation, these roles can be parcelled out across several servers. Microsoft’s restrictions on SBS can be overcome –
as the SBS licence allows FSMO roles to be temporarily transferred to other servers for the purpose of server migration and major hardware upgrades. You can continue to run SBS for up to seven days (there is an option to install an update that extends this
to 21 days) with the FSMO roles on other servers. Don’t let the migration drag on as after that point, the server will reboot every hour, until the roles are transferred back.You’ll need to be logged in to your SBS server to move the Schema Master
to the Windows Server 2008 machine. Start by registering SCHMMGMT.DLL. This allows you to use the Windows Schema Master management tools to transfer the Schema Master role to the Windows Server 2008 machine. Open a command line and type the following command.regsvr32
schmmgmt.dll
You’ll next need to open the Windows Management Console. Once you’ve done this, by typing
mmc at a command prompt or from the Run option on the start menu, you can load the Active Directory Schema management snap-in. From the File menu click Add/Remove Snap-in. This opens a dialog box where you can choose to add the appropriate
tools. Choose Active Directory Schema. This will load the schema management tools, which you can use to move the Schema Master to a new machine.In the Schema Manager console, right click on Active Directory Schema and then choose Change Domain Controller.
You’ll see a list of available servers. Choose the new Windows Server 2008 machine, and then click Change to move the Schema Master role to your new Exchange machine. Right click Active Directory Schema again, and choose Operations Master. This allows
you to make the new server the operations master for the FSMO role we’ve just transferred.
Now you can start the Exchange 2007 installation. Log on to the server, and load the Exchange 2007 DVD; using an Exchange 2007 SP1 DVD reduces the amount of time you’ll need to set aside for downloading and installing uploads. Choose the appropriate Exchange
installation for your network needs – a typical install with Hub Transport, Client Access and Mailbox roles should be sufficient for most small networks. Once Exchange has installed, restart the Windows Server 2008 machine and then open the Exchange
Management console to confirm that your install completed successfully.You will now have added your new Exchange server to the existing SBS Exchange network. On the SBS server open the Exchange System Manager.Expand the Administrative Groups tab to see the
available administrative groups. Your new server should have added itself as Exchange Administrative Group (FYDIBOHF23SPDLT). Do not move it out of this Administrative Group or the associated routing group, Exchange Routing Group (DWBGZMFD01QNBJR) –
these are required to allow Exchange 2007 to interoperate with Exchange 2003. (As a side note, there’s definitely a sense of humour in the Exchange team at Microsoft, as the default administrative group and routing group names are both Caesar Ciphers
of EXCHANGE12ROCKS).If you’re planning to run the two servers together, you can now move the Schema Master FSMO role back to the SBS server; if you’re not, you now have seven days to finish your complete server migration before the reboots start.
To move the role back use the Active Directory Schema MMC snap-in and change both Domain Controller and Operations Master to point to your SBS server.Now you can start to move mailboxes between the two servers. This is where things can start to take time,
so schedule mailbox moves for evenings and weekends – and make sure that you’ve backed up all the existing mailboxes before you start the migration.
You’ll also need to make sure that both servers have the same mailbox size limits – otherwise large mailboxes will fail to move successfully. If you’re unable to make moves at night, you can do them during working hours –
but users will be unable to connect to the Exchange server while their mailboxes are being transferred (remember to warn them in advance). Any mail that’s been delivered to the server during a mailbox transfer will be queued and delivered once the mailbox
is on the new server.
The actual process of moving mailboxes from the SBS Exchange 2003 server to Exchange 2007 is relatively simple. Log on to your Exchange 2007 server, and open the Exchange Management Console. Expand Recipient Configuration, and select the Mailbox
view. This lets you see the organisation’s mailboxes, along with where they’re currently stored. A pane on the right gives you various Actions you can perform on the mailboxes. These include the Move Mailbox wizard.
This wizard is the simplest way of moving mailboxes between servers – and, along with the underlying move – Mailbox PowerShell commandlet, is the only supported way of moving mail to an Exchange 2007 server. If you’re moving a large set of
mailboxes it’s worth writing a PowerShell script to handle the move for you.
Use the Move Mailbox wizard to move either an individual mailbox or groups of mailboxes (shift-click to select several at once). As the wizard is multi-threaded it can handle up to four mailbox moves at once. First select the target database, and then choose
the move options. You can choose to abort the move if corrupted messages exist, as well as choosing the appropriate Active Directory servers. You can also schedule the moves for out of hours – so you don’t have to be on site for a move to take
place – as well as making sure that any moves that haven’t taken place inside a set time limit are cancelled. The wizard will check mailbox quotas before making a move to make sure that the system limits allow the mailbox to transfer to a new server.
Once a move’s started you’ll see a progress bar showing the status of the move, with descriptive text for the current step in the move process. When a move completes there’s a summary screen with the results. There’s also an XML
format report you can use for further analysis.
We found that a large 4GB mailbox took about 3 hours to move, over a gigabit network. In practice, most mailboxes are a lot smaller, so expect to be able to move many more SBS mailboxes in a single overnight session. Once the mailboxes have been moved, your
Outlook users will automatically be switched to the new Exchange server. There’s no need to change anything on the desktop – the Exchange organisation will handle the changes for you. There’s one exception; if you have used a self-certified
certificate for the SBS Exchange server, you may need to delete it from all client devices (including Windows Mobile) so they can connect – especially if you’re using the same external DNS name.While Outlook handles the changes gracefully, things
aren’t so easy for users working with ActiveSync connections to mobile devices or for secure IMAP and POP3
connections. Mobile users will need to perform a manual sync on their phone (they’ll get a message in ActiveSync reminding them to do this) and accept the server policies before mail will start arriving. POP3 and IMAP connections will only continue
to work if you make sure that your new mail server has the same external CNAME as the old SBS install. If you’re not using the same DNS name, you’ll need to recreate connections for external mail clients.
Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

SBS 2003 - Usage Server Report

Hello,
We use the
SBS 2003
server (+Exchange server
2003). We use Outlook Web Access.
Unfortunately in the "usage
report
server"
does not show the
statistics
about the activity of
OWA.
Could you
advise
How to
solve this problem.
Thank you in advance
J.Zabransky

Hi J.Zabransky,
Just addition. Please re-run the Monitoring Configuration Wizard to enable and configure report preferences
or other monitoring features again. Then monitor the result.
Please also refer to following articles and check if can help you.
Understanding the server usage
report
Using the Monitoring Configuration
Wizard
If any update, please feel free to let us know.
Hope this helps.
Best regards,
Justin Gu

SBS 2003 server admin rights dont work access denied on VSS and Network settings

Hi I have just taken over support for a company and have inherited a SBS 2003 Server.
The server has had no backup for over a year (when the last admin left).
VSS does not work, so the back does not work, unable to install any other backup as no admin rights.
I want to repair it so I can do a backup to move to a new server.
I did not know the administrator account password (the last admin didn't tell anyone)
So I used a password reset boot cd and then restarted Windows 2003 in Directory Service Restore Mode.
Copied SRVANY and INSTSRV to a temporary folder, mine is called D:\temp. Copied cmd.exe to this folder too. Next ran at a command prompt instsrv PassRecovery "d:\temp\srvany.exe"
next
Started Regedit, and navigated to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\PassRecovery
Created a new subkey called Parameters and added two new values:
name: Application
type: REG_SZ (string)
value: d:\temp\cmd.exe
name: AppParameters
type: REG_SZ (string)
value: /k net user administrator 123456 /domain
"123456 is substituted for the password I used" Im not daft enough to publish it lol
Next
opened the Services applet (Control Panel\Administrative Tools\Services) and opened the PassRecovery property tab. Checked the starting mode is set to Automatic.
to the Log On tab and enable the option Allow service to interact with the desktop.
Restart Windows normally, SRVANY run the NET USER command and reset the domain admin password.
OK so now I am logged in as administrator but guess what I still don't have admin rights???
I can add new user with admin rights and log in as them but they still don't have admin rights Im totally lost??????????? Help please

I'm thinking the previous tech may have renamed the built-in domain Administrator and then created a new account called 'administrator' with lesser rights? He then used another domain admin account to manage the server.
If so, and given the fact that you don't know any domain admin account usernames or passwords, I think you may be in for a move to a new server without a proper NT backup of the SBS 2003.
However, If you can at least log into the SBS 2003, I wonder if you could download and run DIsk2VHD and create VHDs (not VHDX) of the current SBS 2003 drives, saving them to an external USB drive connected to the server.
You could then 'attach' the VHDs to a Win7 Pro computer and gain access to the files/folders, although not the Active Directory stuff. Moving Exchange and Sharepoint would impose additional pain. For Exchange, you could log
onto workstations as each user and export their Exchange mailboxes as .PSTs. I believe you could do the same with any Public Folders.
Disk2VHD
http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx
How to Mount a Virtual Hard Disk in Windows 7
http://www.online-tech-tips.com/windows-7/mount-vhd-windows-7/
Of course, the owner could also have his attorney contact the previous tech and threaten legal action unless he coughs up the correct domain admin username and password. That username and password belong to the owner, not the
tech.
Merv Porter
=========================

SBS 2003 Server & email

Hi everyone!
This is my third post regarding not being able to set up my email and I found out a little more info today. We are using SBS 2003 for a server and this is maybe why I'm having problems. We use excange and access our email with Microsoft web access away from the office. I was told that I may have to buy additional software and run a seperate computer just for the Blackberry. Does anyone know if this is true? The problem is that I keep getting a message saying a connection could not be made and to check the server name is correct and available. I know the server name is correct. We have a small office and ther will only be 3 of us using Blackberries. I told my boss how nice they are and easy to use so I'm trying to not eat my words. If anyone can help I sure can use it.

I have read your older posts as well. I would suggest calling your service provider BB support, and since you cant set it up, they will transfer you to RIM support, who will give you the root cause of the issue.
Now as a workaround you can create a blackberry.net email address on your BIS account and change the reply to address to your '[email protected]' address and then set up forwarding rule on your exchange server. Hope this helps.
Click on KUDOS to appreciate our efforts and mark the thread RESOLVED if your issue is resolved.

How to create ADC in SBS 2008 64 bit Server for SBS 2003 32 bit Server?

Hi,
We have single windows SBS 2003 32 bit server with AD to run database as well as application of the Company. We are planning to add one more server to the network with SBS 2008 64 bit for load balancing. I just confused that two SBS servers are not compatible
in the SBS network. my requirement is to balance the database and application request load balancing along with fail over management with two Servers in the network.
Please let me know the procedure to add the SBS 2008 64 bit server as Additional Domain Controller to SBS 2003 32 bit PDC so that ADC to take role if PDC fails.
Any other ways to meet my requirement?

Hi Mallensh Patil,
Would you please let us know current situation of this issue?
I agree with Cliff. Just addition, please also refer to following article and check if can help you.
Debunking Myths About Additional Domain Controllers In SBS Domains
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Migrate SBS 2003 to Windows Server 2012 Standard

We currently have two servers (SBS 2003 Standard utilizing Exchange 2003; Windows Server 2003 R2 Standard with SQL 2005).
We want to retire the SBS or maybe both.
We have purchased a new server (Windows Server 2012 Standard with licenses for Exchange 2013 and SQL 2012).
Is there a whitepaper that describes how to migrate SBS 2003 to Windows Server 2012 Standard?
Is it possible to run Exchange 2013 on the Windows Server 2012 box? In Hyper-V? If Exchange can run in a virtualized instance, do we need additional licensing to run another instance of Windows Server 2012 Standard?
Can we run SQL 2012 on the same Windows Server 2012 box?
We have about 35 users.

Sal,
Migration went fine. Steps i took:
Join 2012 Standard server as member.
Migrated roles.
I ended up manually creating new shares. The old environment was a mess.
Robocopy data/verified.
Seize FSMO roles
http://support.microsoft.com/kb/255504
Metadata cleanup
http://support.microsoft.com/kb/216498
Good luck

Conecting to the internet Via a SBS 2003 Windows server

I have 2 macs connected through a 10/100 tbase switch and a SBS 2003 windows server also connected to the switch. The widows server is what accesses the internet. how do i get the macs to pick up the conection???

Hi, and a warm welcome to the forums!
http://www.chicagotech.net/icssetup.htm
http://support.microsoft.com/kb/324286
http://www.ifelix.co.uk/tech/index.html

Server SBS 2003

Similar Messages

Maybe you are looking for