Migration of SBS 2003 Network to Server 2008 Std

-

i looking migrate server 2008 network.  right main server sbs 2003.  domain controller on network.  serves files on network.  have second server running 2003 std that exchange server running exchange 2003.  system serves website iis. 

my primary concern @ time migrate sbs 2003 system on server 2008 std.  put new server alongside existing.  i have done many times server 2003 std adding new domain controller , replicating data , demoting old server.  since sbs 2003 needs @ top of forest procedure moving master roles same?  can away sbs 2003.  secondly since has first exchange server part server 2003 sbs, i want make sure don't break actual exchange on member server.  looking proper migration path adjustment.  or direction great.

hi,

 

thanks post.

 

from description, understand migrate sbs2003 system on windows server 2008.

 

as know, exchange server installed on dc machine part of sbs2003; however, mention have second server running windows server 2003 std exchange server running exchange 2003.

 

if second server running windows server 2003 std deals mail service, add new domain controller , replicating data , demote sbs2003.

 

for more information, may take @ following article:

 

adding server running windows server 2008 windows small business server 2003 network

http://technet.microsoft.com/en-us/library/cc708131(ws.10).aspx

 

if exchange server installed on dc machine part of sbs2003, may break exchange server when performing above steps.

 

in case, you may wish post sbs 2008 newsgroup. provide access others read public newsgroups regularly either share knowledge.

 

connect windows small business server 2008

http://connect.microsoft.com/sbs08

 

or may post new thread our exchange forum exchange migration issue.

 

exchange migration forum

http://social.technet.microsoft.com/forums/en-us/exchangesvrmigration/threads

 

hope helps.

 

best regards,

 

miles zhang

windows server forum

if have feedback on our support, please contact tngfb@microsoft.com 

 

********************************************

hope can receive more , more feedbacks satisfied customers. :-)



Windows Server  >  Migration



Comments

Post a Comment

Popular posts from this blog

DCOM received error "2147746132" from...

-
hi everybody, i have dc (my windows essentials 2012 server) , windows 2012 server in network.  the windows server 2012 inside domain. on server, got "non stopping" error says in event logs : ===> dcom received error "2147746132" fromd computer xxxx(my dc computer) while server trying activation : {6df8cb71-153b-4c66-8fc4-e59301b8011b} it never stops, got 11000+ new events :s i found : http://support.microsoft.com/kb/971153/fr i'm not sure should ? does got idea ? matthieu. hi, please try solution mentioned in below link: http://www.eventid.net/display-eventid-10006-source-dcom-eventno-272-phase-1.htm regards, cicely Windows Server  >  Windows Server 2012 General ...
Read more

DFSR RPC replication errors 5014 1726 with large files over VPN

-
i have similar issue ryan in reply http://social.technet.microsoft.com/forums/en-gb/winserverfiles/thread/6d49fd71-2236-4fcb-9763-bf1c03459ee8 cited below. start additional thread here because other 1 related windows server 2003 (r2) , i'm (as ryan) on windows 2008 r2 x64. here first of post ryan: i've got same problem on 2008 r2 dfsr server.  the spoke server has 2x intel 1 gigb on-board nics in active/standby teamed configuration. the hub server (running on vmware using 10gbit vmnet3 nic driver) logs dfsr event 5014 every 2-15mins (usually around 5mins). the spoke server not log event. replication running slowly. initial sync/replication. had re-configure replication folder because of lost dfsr database on spoke server.  could teamed nic on spoke causing error on host? a note: last time did initial sync on folder processed @ 30k files , hour. time it's doing few hundred and hour. another note: hub server has several replication groups , conne...
Read more

ADFS 3.0 Event ID 4625 | An Error occurred During Logon | Status: 0xC000035B

-
we're getting these random errors on our adfs security logs, how can track down generating them? an account failed log on. subject: security id: null sid account name: - account domain: - logon id: 0x0 logon type: 3 account logon failed: security id: null sid account name: account domain: failure information: failure reason: an error occured during logon. status: 0xc000035b sub status: 0x0 process information: caller process id: 0x0 caller process name: - network information: workstation name: - source network address: - source port: - detailed authentication information: logon process: kerberos authentication package: kerberos transited services: - package name (ntlm only): - key length: 0 event generated when logon request fails. generated on computer access attempted. subject fields indicate account on local system requested logon. commonly service such server service, or local process such ...
Read more