Anyone connected MBP to SBS 2003?

I will be connecting mine when I get it to a Small Business Server 2003...I just want to be ready to address any issues.
Thanks

You might consider taking this question to:
http://discussions.apple.com/forum.jspa?forumID=1153
which is a more appropriate place for networking questions. I think there might be a different "audience" on that part of the forum.
Bob

Similar Messages

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?

Can't connect to windows sbs 2003 using Leopard...

Hey there...
I'm one of 3 Mac users at our office. We use Windows Small Business Server 2003.
Since upgrading to Leopard, I can no longer access the network shared folders. Didn't even think about this when upgrading. Our IT guy is strictly a Windows user and is no help in the matter.
Any thoughts (other than re-installing Tiger)?
Andy

The genius for Microsoft products an be found onthe Microsoft forums for their Mac software:
http://answers.microsoft.com/en-us/mac

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.

Error connecting win 8.1 to sbs 2003 vpn

When I attempt to connect my (all antivirus off, firewall off, ports forwarded, gre enabled) win 8.1 laptop to my office sbs 2003 machine through a pptp vpn, I get an error. Here is the log:
[cmdial32] 21:34:36
11 Custom Action Failed
ActionType = Connect Actions Description = Configure proxy settings for IE. ActionPath = C:\Users\******\AppData\Roaming\Microsoft\Network\Connections\Cm\REMOTE\CMPROXY.DLL. This action either could not be loaded, or failed to run.
[cmdial32] 21:34:36
21 On-Error Event
ErrorCode = 1157 ErrorSource = Configure proxy settings for IE.
Any ideas? Thanks in advance.

Hi,
Regarding the current issue, please try to refer to the following similar thread to see if it works.
Windows SBS PPTP VPN Issues
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_23198820.html
In addition, I suggest you could refer to the following method to join it to the domain over VPN.
Joining a computer to a domain over a client VPN connection
https://msmvps.com/blogs/acefekay/archive/2012/01/18/joining-a-computer-to-a-domain-over-a-client-vpn-connection.aspx
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

Connecting to SBS 2003

Hi everybody,
I am a newbee to the Mac environment. I would like to connect my brand new macbook air to my SBS 2003.
So I created a computer profil on my SBS.
Now, is there a tutorial to connect my Mac to my SBS ?
Thank you for your help.
Pascal

Welcome to Apple Discussions:
Check out this MS page
http://www.microsoft.com/downloads/details.aspx?FamilyID=89EE677B-0FF6-4558-A54B -6070E2C8CD65&displaylang=en

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.

SBS 2003 R2 premium (with ISA 2004) Exchange ActiveSync not working

A client has a SBS 2003 R2 premium (with ISA 2004) and wants to sync iPhones and Android phones.
When using the Microsoft Remote Connectivity Analyzer and selecting 'Exchange ActiveSync' we get 'The test of the FolderSync command failed. Exchange ActiveSync returned an HTTP
500 response.'
We tried every solution we could find on the internet, without success.
This is what we tried and checked so far:
- fixed IP, DNS, trusted SSL (comodo) seem all OK
- Exchange 2003 SP2 and ISA 2004 SP3 installed.
- RWW and OWA working fine.
- tests with iPhone and Android -> 'cannot get mail. The connection to the server failed'.
- event viewer reveals no further clues.
- ran CEICW several times enabling and disabling most remote options (OWA OMA,...)
- manually checked all vDir settings in IIS6
- tested with different accounts, created a testaccount without any administrative privileges in Active Directory.
- surfing to servername/microsoft-server-activesync from local network and to domain/microsoft-server-ActiveSync from external computer both give: HTTP 501/HTTP 505 error as expected.
- reset the default virtual directories
- on ISA a query by dest port (443) shows traffic reaching the ISA server ending in:
Log type:
Web Proxy (Reverse)
Status:
500 Internal Server Error
Rule:
SBS OMA Web Publishing Rule
Source:
External ( XX.XX.XX.XX:0)
Destination:
( XX.XX.XX.XX:443)
Request:
POST
Filter information:
Req ID: 1c6d0bea
Protocol:
https
User:
anonymous
Could anyone give me any pointers on what I need to do to get this working please?
Many thanks in advance for your assistance.
Regards
Jean-Paul Laffargue
ARCOM BVBA

I used to have a SBS2003 on ISA running activesync with no issues so I'll try and give you guidance although it's been a while. I gather this is the first time use of this feature on this SBS? If so make sure you follow the instructions here:
http://technet.microsoft.com/en-us/library/cc182239.aspx
Also make sure you've enabled all mobile services in exchange features and updated your users with the Mobile User profile (I think they need to be members of the Mobile and Remote Web Workplace groups in Manage Users IIRC). Anything in the event logs?
Also, for some phones you need to manually download the certificate if you use a self-signed type.
Note that in the end it may be time to replace this soon to be unsupported ISA with a separate firewall (or a "free" Untangle box) and go to a one NIC solution. It simplifies things and you need to do that anyway to transition off SBS2003 when it is
unsupported next year.
-- Al

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.

Moving from SBS 2003 to Hyper V 2012 R2 VM's

Hi Folks,
Apologies if I have posted on the wrong Forum
I will keep this brief .
My customer currently has an old SBS 2003 standard physical server. They utilize the integrated Exchange 2003 system. It now needs to be changed/upgraded due to lack of hard disk space and incompatibility between Outlook 2013 and exchange 2003 amonst other
thing.
SBS is no longer available but as the company has grown substantially in the last few years SBS would have been unsuitable anyway. The company has about 80 user accounts across 60 Computer systems.
I have decided after much research to replace the old SBS2003 system with one new Physical server running Windows 2012R2 Hyper V as the Host O/S.. I have also setup 2 Gen 1 VM's running Server 2012 standard, (NOT 2012 R2). I have then promoted one of the
VM's to be a domain controller simply by adding Active Directory Domain services role. The othe VM will be used as an exchange 2010 server .. I have the Exchange 2010 SP3 installation lying in wait on the second VM but I havent installed yet as it requires
access to domain accounts.
The new Server has about 1 terabyte of Hard drive space and 32 gig Ram. The DC has been allocated 8 gig of Ram and 500 gig of Hard drive space. The exchange 2010 VM has been allocated 12 gig Ram with 150 gig Hard drive space.
What I need now is a guide on how to get this new server installed on my existing network and removing the existing SBS2003 box.
I know i have to attach the new domain Controller VM to the existing domain and allow active directory account information etc to replicate onto the new DC VM. Apparently this can take a few days. I am unsure however at which point I connect the exchange
server to the old sbs2003 box in order to move the mailboxes.. actually I am not even sure if I ever connect the new exchange VM to the old sbs 2003 box. Would it be better to get the DC replaced first. i.e attach the DC to the existing domain.. let the active
directory info to replicate.. transfer the roles, demote the sbs2003 box?? I am concerned that the old mailboxes on the sbs2003 box will then be irretrievable..
Perhaps someone can clarify the steps in sequence that I need to follow to end up with my DC VM and Exchange 2010 VM with migrated mailboxes installed as replacement for the current sbs 2003 box.
Some other notes: Although i have used 2012 R2 for the hyper V host I have decided that 2012 made better sense for the VM operating systems due to the better compatibility with exchange 2010 in one VM and simply because of online advice on the DC VM.
Thanks in advance

This doesn't really have anything to do with Virtual Server 2005 (this forum, or even Hyper-V).
This is migration from SBS to a regular domain. Look at the SBS forums, or Exchange and AD forums for advice moving from SBS to regular Exchange and 2012 AD.
Maybe here:
http://social.technet.microsoft.com/Forums/exchange/en-US/3fae661d-1c34-4728-96ce-7eaf79af64c3/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2?forum=exchange2010
http://technet.microsoft.com/en-us/library/jj200112.aspx

Connecting mbp 15 inches intel 2.53ghz to 40 inches full hd samsung lcd

hiii i want to connect my connecting mbp 15 inches intel 2.53ghz to 40 inches full hd samsung lcd
which wire or what peripherals i have to buy

i got exactly the same problem. i have a samsung le32c530 lcd, but sometimes works sometimes not. when i plugged the first time mac to the lcd everything worked. this problem appeared when the mac went to sleep mode.
after trying everything i put this working honestly i dont know what i made, but now the same happened and i cant solve this...
anyone can help us?
i use a macbookpro late 2009, with a dvi-hdmi cable.
Message was edited by: elioc9

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

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

SBS 2003 SP2: VSS errors; unable to create system state backup (NTBACKUP)

NTBACKUP system state on W2k3 server fails after "thinking" for ~10 mins and "creating" shadow copy; almost no disk activity, almost no CPU load. Errors in the Application
log:
Source: SQLVDI EventID: 1
Loc=SignalAbort. Desc=Client initiates abort. ErrorCode=(0). Process=3392. Thread=29348. Client. Instance=. VD=Global\{9B35142B-C687-4766-9707-BC387534BA38}1_SQLVDIMemoryName_0.
Several of them.
Then:
EventID: 8019
Source: NTBackup
End Operation: Warnings or errors were encountered.
Consult the backup report for more details.
Then:
Source: VSS
EventID: 12305
Volume Shadow Copy Service error: Volume/disk not connected or not found. Error context: CreateFileW(\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9,0xc0000000,0x00000003,...).
And finally:
EventID: 12293
Source: VSS
Volume Shadow Copy Service error: Error calling a routine on the Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details PostFinalCommitSnapshots({de0d580b-68ce-4eae-a046-b5b5b7a80235}, 1) [hr = 0x80042308].
When creating shadow copy on the system volume, the operation may take ~40-90 mins. On the data volume -- <1 min.
"vssadmin list writers" shows:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'SqlServerWriter'
State: [10] Failed
Last error: Retryable error
Writer name: 'MSDEWriter'
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'NTDS'
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Event Log Writer'
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Certificate Authority'
State: [10] Failed
Last error: Retryable error
Writer name: 'WINS Jet Writer'
State: [10] Failed
Last error: Retryable error
Writer name: 'Registry Writer'
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
State: [1] Stable
Last error: No error
Writer name: 'TermServLicensing'
State: [10] Failed
Last error: Retryable error
Writer name: 'WMI Writer'
State: [10] Failed
Last error: Retryable error
Here is what I tried to do:
1. Restarted that thing.
2. Cleaned the security log.
3. Installed Windows Server 2003 Hotfix rollup KB940349-v3.
4. Stopped both SBSMONITORING and SHAREPOINT instances of MSDE, SQL 2005, SQL 2005 VSS and tried to perform the system state backup then. Stopped Exchange 2003 before launching NTBACKUP as well.
5. "regsvr32 sqlvdi.dll" in MSDE directory.
6. Renamed "System Volume Information" on all volumes and VSS has re-created them.
7. chkdsk /f was fun on all volumes, no major issues found.
8. Installed Hotfixes KB967551, KB975928-v2 (someone recommended).
9. Disabled SQL Server VSS Writer (SQLVDI errors disappeared from the application event log, VSS and NTBACKUP errors stayed).
10. Re-registered the DLLs as per Shaon Shan's post at http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/346fa42c-a476-457f-bcf3-59f87e444b55
The above had no effect on the issue whatsoever, except a little change at item 9 as mentioned.

Hi there.
I just had that problem. I saw friday my backup from my sbs 2003, was not completing becasuse it said it couldn´t creat a shadow copy in the external drive... It kept giving me errors os VSS and Volsnap... But strange thing is, i have VSS turned off in all
drives, and from months no problems with backups... So i went in Event viewer and look at it with attention, i saw a error that keep coming up from time to time (because we change the external drive form week to week). And i realize that there's a disk error
event...
Couldn´t run checkdisk from server, dont now why.. So i disconnected the drive, connected to my laptop, and ran a CheckDisk /F /X. ... It had BAD SECTORS! So i ran check disk... waited like 10-20 minutes. And then i ran it again just in case, and the 2nd
time was much more faster, like 3-6 minutes.
I disconnected from laptop, and connected to server. I went to the Backup wizard (in server managment), and press Backup now...
It hang 5-10 second in Creating Shadow copy..... And it started making the Backup :_D
I've seen all errors that were reported exactly as mine. I ran the Hotfix, all stayed the same, i followed all manual steps and still the same... and the problem was always in the external drive, which had bad sectors.
Hope it will help the next person that needs this info!

Anyone connected MBP to SBS 2003?

Similar Messages

Maybe you are looking for