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.
Similar Messages
-
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 pleaseI'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
========================= -
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 -
The company I work for uses MS Exchange 2003 Server for its email. iPhone with either iOS 4 or iOS 5 does fine synching with Exchange 2003. I would like to access my work email on my Mac. Microsoft says that the only way to do this is to buy MS Office 2008 Home Business Version, and as far as I can tell, this is correct. Does anybody know of a workaround, perhaps syncing my email from iPhone to Mac. Thanks.
KiltedTim wrote:
My bad. I seem to recall, though setting up mail to talk to our Exchange 2003 server before we migrated over to Exchange 2010 this year. My memory of the timing must be off.
There's always OWA in a pinch.
Not for Exchange 2003 users, /OWA came in with 2007 sp1 and all that, before that it was /exchange. Everyone is dropping support for E2003, even Microsoft (see Outlook 2011), Entourage is actually a good client, different, but better than it looks. You can also use 3rd party connectors, DavMail is a common choice but I found it close to incomprehensible, and then unreliable (especially with contacts) -
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?
-
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! -
OWA is not receiving emails // SBS 2003
Hi Guys!
I have a following problem on my SBS 2003 Server, I do not receive emails when I access my mailbox with Outlook Web Access from home or any remote location. But if the outlook on my workstation is left on it is ok, mails are popping up right away on the
OWA too.
It was working great for me for many years.
I looked over the internet but nothing seemed to help yet...
I deleted and then created new .ost file, I have cashed mode switched off, I deleted forwarding rule that I had to my private account.
Do you have any ideas what might cause this?
Any help would be appreciated!Most interesting. From the sound of it your Outlook is somehow set to trigger the release of mail into the Exchange server, which I have never seen. Whether SMTP or POP3, mail should arrive at the Server and OL or OWA are just "windows" or "periscopes" to
allow viewing. Is it possible that your Outlook is popping for the mail and the default mailbox is the Exchange server?
For your home copy of OL, consider Outlook Anywhere instead of VPN. VPN's are old school and expose your business network to any nastiness that creeps into your remote systems. You will find instructions on the RWW landing page.
For SMTP... you should have a static IP at the office, forward port 25 from your edge device/firewall/router to the ip of your SBS, then change your MX record at your public DNS host to point to your public IP (some use A records for the IP and the
MX points to the A record, some use IP numbers, check with your DNS host), then run the CEICW wizard specifying SMTP mail.
As for mail getting lost or something going wrong.... yes it can. But so can POP3. Historically there have been more issues with POP3 than SMTP. Consider that only the smallest of the organizations would use POP3, that every business larger
than those in the SBS space uses SMTP and you get the idea. SMTP is "store and forward", meaning if your system is off line for some little time the mail will still come. Usually it will not be returned to sender for about 48 hours, which is sufficient
time to get the SBS back on line or to change the MX record back until it is. There are also web services that will act as backup mail servers and hold your mail, some that will allow "Web Mail" access to it, and some that will do both and are very low
cost or even free.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit. -
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 -
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,
Mikehi
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.ZabranskyHi 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 -
Migrate SBS 2003 with AD and Exchange to Windows Server 2012 Standard
We are using SBS 2003 and we have configured Exchange server and AD with DNS and DHCP. Now we are planning to move SBS 2003 to Separate servers like windows server 2012 standard AD with DNS and DHCP and Windows server 2012 Standard with Exchange
2010.
Is it Possible?? we need step by step guide.
Thanks in advance.Hi,
You probably would not find any step by step guide for this kind of migrations. If you are not comfortable with doing such migrations I would recommend to if you need to do it your self do some test migrations. Or otherwise get help by a local IT company
that is familiar with migrations.
But to give you some information, first thing before starting a migration is check the health of your SBS 2003 server / domain. Use tools like dcdiag, netdiag and best practice analyzer. I wrote a blog post about steps to think about before you start this
might help: http://blog.ronnypot.nl/?p=914
When every thing is clean you can start adding the new windows server 2012 machines as member servers to your domain.
Next you can promote one of the servers to additional domain controller on your domain (Keep in mind SBS needs to hold all FSMO roles so moving these is the last step your should do.) Also promoting a windows server 2012 to domain controller has slightly
changed, you need to install the ADDS role and follow the wizard to promote the server to a DC.
With installation of the new DC install DNS allongsite it will automatic replicate settings during confiugration.
DHCP must be installed manual, depending on your scope and settings it might be as easy to create a new scope and disable the old dhcp server.
On the server Exchange needs to be installed, make sure you install and do all pre-requirements. Than install Exchange it will automaticly detect you already have an Exchange organization and is installed as additional server. You can configure all settings
and when everything is configured right you start moving mailboxes.
When everything is moved away from the SBS 2003 server, uninstall exchange, move the FSMO roles to the new DC and after that demote the sbs 2003 server so it is not listed anymore as an additional DC in the domain. Last would be shutdown the server and remove
all records left in AD and DNS.
There is this guide for migrating SBS 2003 to windows server 2008 R2 and Exchange 2010, this might give you some usefull information, not everything will be the same but it is a good start:
http://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/
Regards Ronny
Visit my Blog or follow me on
Twitter -
Best way to sync Outlook 2007 calendar with Exchange on SBS 2003
I currently have Vista and Outlook 2007.
My email, contacts and calendar are all in a OST file, which syncs to our Windows SBS 2003 server and the Exchange installed on it.
How should I configure my iPhone and iTunes, in order to have my calendar in iPhone?
After trying for several times to sync through iTunes without any success (could never have any items imported to the iPhone) I did create an Exchange account on my iPhone with the IP address of our SBS server, and my account details, and now all my items seem to appear (however they all have Accept/Maybe/Refuse buttons).
Is this the correct way? Will I get alarms for my appointments, even if I don't accept them on the iPhone?
Thank you!OK, I think I figured it out, with Apple's iCloud instructions and a little help from campus tech support. This only applies to people using Outlook with Microsoft Exchange.
Enable iCloud on your computer (running Lion) and your iPhone. http://www.apple.com/icloud/setup/mac.html
Then go to your iPhone's Mail icon, click on Add Account > Microsoft Exchange and enter your login info.
Doing this transferred my work email and calendar to my phone wirelessly. -
Client PC migration fails from SBS 2003 to SBS 2012 Essentials
Please check out this entire message before making an assumption about what it says, thanks.
Our old SBS 2003 Server hard failed a few weeks ago.
Rather than repair it, we ordered a new server with SBS 2012 Essentials and loaded the backup data from the old server.
The Server is just fine. We are having no issues whatsoever with the server. I kept the old domain name and server name.
The Client Computers, some Win7 some Win8.1, have turned into a nightmare to re-connect.
What happens is, the user can log in, but has no files in desktop, downloads or documents, nothing has been migrated:
The process I'm using is this:
1> I take them off the old domain and set them up as workgroup: NOGROUP... that works fine.
2> I bring up http://SERVERNAME/connect and begin installing the server software, no problem yet...
>> This goes to a point where it asks for a restart, followed by a lot more waiting.
>> Eventually it crashes with a message I have, unfortunately, not documented (sorry).
3> When I restart the PC, I'm able to log into the user account : DOM\username, but none of the users files are there.
Looking at the file tree at C:\Users I see a folder structure like this:
C:\Users
|_ _client.setup_ (essentially empty)
|_ username (the old account... and yes, it has all of the files and app data)
|_ username.DOM (the new account, but essentially empty)
It appears that the setup was supposed to migrate 'username' thru '_client.setup_ into 'username.DOM' but failed.
I can move all of the data from 'username' to 'username.DOM' to solve the data and files problem.
But the AppData folder cannot be moved in its entirety (I tried, and it clobbers the user completely), I have to manually transfer files from 'username\AppData' folders (Local, LocalLow and Roaming) making sure to transfer only the files that don't exist
in the 'username.DOM\Appdata' folders.
I realize that this process leaves me with a 'Less Than Perfect' AppData setup.
Since I have many Clients left to convert, I'd like to know if I'm doing something wrong, or how to make it right.With a new server with a new domain you have started down the right path. Disjoin and the http:// technique should have worked, but we can address that when you can give us more info.
When joining a new domain the old users profiles get blocked by security to the new users. But the local admin or the domain admin should have access. The way I do it is to copy out the required data from the old profile to a safe place then
copy it back to the new profile when finished. But there are profile migration wizards, one of them at
www.forensit.com, that work very well.
As for the system crash when you did the join... please see if you can get the message, and then examine the logs in both the server and the client. For the server, look here:
http://blogs.technet.com/b/sbs/archive/2014/09/30/windows-server-essentials-log-files.aspx
For the client, scroll down in the link above to the section about client side logs.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit. -
Attempt to access external website keeps getting grabbed by SBS 2003
Hi folks,
I have an old SBS 2003 server that recently switched their external web hosts. They are configured with the same FQDN for both their active directory domain and their public domain (westsidebaby.org). I went into DNS on the SBS server to simply update the
WWW record and the Windows DNS equivalent of the domain @ record. Now when any internal network user tries to access the website, they get the Welcome to Small Business Server 2003 page on the local IIS. External users can get to the website no problem.
There is also an A record for partners.westsidebaby.org in the internal DNS that points to their old web server and that resolves just FINE. NSLOOKUP from both the server and internal clients to the local DNS server give me the correct external address.
Pinging www.westsidebaby.org from the local subnet resolves correctly as well. I have done ipconfig /flushdns on the server, as well as the clients I am testing, flushed/deleted/cleared the caches and browsing histories from the various browsers (IE, Chrome
and Firefox), all in very logical, intentional order before attempting to type the addy.
If I change a client's DNS server to an external source, I can resolve to the new website just fine. Just can't access AD or server shares any more. Ugh.
No matter what I seem to do, barring resolving through an outside DNS server, typing www.westsidebaby.org from inside still gives me the dang SBS page. I have also setup a HOSTS file to no avail. OMG, I am FIT TO SPIT. Any ideas?Hi,
This is happening because of DNS misconfiguration. Try and stop Default Website as a test and browse the site. Also check if there is a host header on Default website pointing to westsidebaby.org
Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help. -
Windows 7/SBS 2003 Networking Issue complicated by Verizon Router
I posted on Answers.Microsoft.com ( http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/windows-7-suddenly-wont-talk-to-sbs-2003-server/e8116774-6b4f-44d3-91cf-b10df236805a?tm=1405553282721 ) and here at TechNet in the Windows 7 IT Pro
forum ( http://social.technet.microsoft.com/Forums/en-US/1f8b8cbc-4b9d-4f68-981c-4c71e7a3f24a/windows-7-suddenly-wont-talk-to-sbs-2003-server-and-viceversa-possibly-dns-but-not-definite?forum=w7itpronetworking ) a problem that I was having with our Windows
7 computers suddenly losing connectivity to our SBS 2003 server. Someone posted an answer (rebooting our router), which worked, but only on a temporary basis. After turning off the router and turning it back on, we get connectivity back for about 3 days, then
we lose it again, and we have to reboot the router again.
I called Verizon, and the tech I spoke to claims that the problem is that the SBS 2003 server should not be the DNS and DHCP server for the network - the Verizon router should be. He's claiming that the fact that we have IP Address Distribution turned off
on their router means that the router never properly knows where each address is assigned. The fact that this all worked up until a week or so ago, and that it's only the Windows 7 machines that are affected, he doesn't have an answer for.
His suggestions were either A) turn off DNS and DHCP on the SBS 2003 server and have both run through the Verizon router, or B) assign static IP addresses to each machine. From what little I know (I inherited this system from someone who left little or nothing
in the way of technical notes) DNS and DHCP have to be running on the SBS 2003 server since it is a domain controller. B) seems possible, as long as I note the static addresses both on the server and on the router.
This still, however, does not really address the underlying issue. Somehow, I think there should be another, easier way to make this work. Especially since, as I said, these Windows 7 machines were content to run for about a year, and only in the past week
or two started having this issue.
Any help would be greatly appreciated.
============== Brian Gerstel Billing and IT Support, Regional Bankruptcy Center of Southeastern PA, P.C.The LAN is all one subnet (it's not a very big office), a 192.168.1.X network.
I don't think the router's firmware has been updated recently, although I can't swear to what Verizon might have done "behind my back" (they do funny things with some of their routers, from what I can tell),
The router doesn't sit between the server and the clients - it only links our LAN and WAN (there's 1 port on the router hooked to the uplink port of a 16-port Gigabit switch which handles the LAN).
The router is the default gateway for all the systems on the LAN.
When the Windows 7 problem occurs, a Windows XP client can ping a Windows 7 client and vice versa, but a Windows 7 client can't ping the SBS server nor vice versa (and in all cases, I'm pinging numeric IP addresses, not the name). Since the SBS server is
the DNS server, the Windows 7 clients effectively lose the ability to go out on the Internet, although some programs that must cache the data (like Microsoft Outlook) seem to continue working so I think WAN access is still up for them.
Brian Gerstel Billing and IT Support, Regional Bankruptcy Center of Southeastern PA, P.C.
Maybe you are looking for
-
How do I create jump to (page) links using DPS in creating a digital page turner for a catalog?
I know how to use "navto" to jump to pages within the catalog created for our app. We want to use the same article files to create a digital page turner using DPS but cannot figure out how to do it. Google searches lead to answers that say it isn't p
-
My Dropbox files are not synching to my iPad. Is this a common problem and is there a fix?
FFiles I store to Dropbox do jot now appear on my iPad Dropbox app. They used to. If I reload Dropbox then it synchs all but I lose the favourites and when I save my more files they do not synch to this device.
-
Error 1714, 1603 PL install program
When starting the program PL CC an error 1714? 1603 is displayed. Help fix and install
-
does Java 6 only run on 64 bit systems...... From the downloads page, I clicked on system requirements and was taken here: http://java.sun.com/javase/6/webnotes/install/index.html....
-
Error while creating multiple identity realms
Hi, I am trying the tutorial for creating multiple identity realms posted on http://www.oracle.com/technology/obe/obe_as_10g/im/realm_mng/realm.htm While executing "STEP 12" to enter the following values: -User Search Base, -User Creation Base, -Grou