DFS replication between Windows Sever 2003 R2 & SBS

DFS replication between Windows Sever 2003 R2 & SBS

Post by VmFuQk » Fri, 11 Jul 2008 03:57:01


Hello,

We have a Windows Sever 2003 R2 Standard Edition SP2(hostname is Mars)
running on Intel Core2 Quad CPU Q6600 @2.4GHz and a Windows Sever 2003 for
Small Business Server SP2(hostname is Doublehelix) running on Dual Core AMD
Opteron Processor 270 @ 2.01GHz. They are on the same sub-network but in
different locations and domains(lakescom.net & blcomfor.local). Each of them
is a domain computer of the other one. Doublehelix has most of our important
data, applications and MSSQL services only.

A fault tolerance/disaster recovery solution is necessary for us. If
Doublehelix goes down, users can still access data and run programs on Mars.

First, we created DFS roots and linked them to share folders on both
servers, and then tried DFS replication group for data collection on Mars but
failed. The error said oublehelix.lakescom.net: the service control manager
cannot be opened. Access is denied We are not sure if the reason is, that
not all new functionality (snap in's) are showing after doublehelix upgraded
to SBS R2, specifically the DFS management console.
Could you please tell me what would cause this problem?

In our case, is the DFS replication possible and enough for us?
If so, how can we implement it?
Does one domain have to be removed?
Do we need to upgrade one or both servers? If so, which edition (2003
Enterprise/2008)?
Is Severs-Cluster or High-Availability system applicable and necessary?
Any other solution available?

Thanks,
 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by Cris Hanna » Fri, 11 Jul 2008 05:25:24

his is a multi-part message in MIME format.


You have two issues
1. SBS 2003 R2 does not contain the DFS-R bits
2. SBS 2003 does not support trusts with another domain.

So if you want DFS-R to work, you'd need another Windows Server 2003 R2 std server in your SBS domain and then the other server would have to belong to the SBS domain.

OR you can run the transition pack on your SBS server and change it to a standard server and then you can support trusts and DFS-R

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"VanBC" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM ...
Hello,

We have a Windows Sever 2003 R2 Standard Edition SP2(hostname is Mars)
running on Intel Core2 Quad CPU Q6600 @2.4GHz and a Windows Sever 2003 for
Small Business Server SP2(hostname is Doublehelix) running on Dual Core AMD
Opteron Processor 270 @ 2.01GHz. They are on the same sub-network but in
different locations and domains(lakescom.net & blcomfor.local). Each of them
is a domain computer of the other one. Doublehelix has most of our important
data, applications and MSSQL services only.

A fault tolerance/disaster recovery solution is necessary for us. If
Doublehelix goes down, users can still access data and run programs on Mars.

First, we created DFS roots and linked them to share folders on both
servers, and then tried DFS replication group for data collection on Mars but
failed. The error said oublehelix.lakescom.net: the service control manager
cannot be opened. Access is denied We are not sure if the reason is, that
not all new functionality (snap in's) are showing after doublehelix upgraded
to SBS R2, specifically the DFS management console.
Could you please tell me what would cause this problem?

In our case, is the DFS replication possible and enough for us?
If so, how can we implement it?
Does one domain have to be removed?
Do we need to upgrade one or both servers? If so, which edition (2003
Enterprise/2008)?
Is Severs-Cluster or High-Availability system applicable and necessary?
Any other solution available?

Thanks,


!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//E>">< < < < < < < You have two issu<s< 1.  SBS 2003 R2 does not contain the DFS-R
bi<s< 2.  SBS 2003 does not support trusts with
another domai<.< &nbs<;< So if you want DFS-R to work, you'd need another
Windows Server 2003 R2 std server in your SBS domain and then the other server
would have to belong to the SBS domai<.< &nbs<;< OR you can run the transition p
 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by Dirk-Thoma » Fri, 11 Jul 2008 05:51:56

his is a multi-part message in MIME format.


Chris... man you read to fast.... he does not have 2 sbs machines, one is Windows 2003 R2 the other SBS 2003 SP2 and the Windows 2003 R2 is setup as a domain controller.

Dirk-Thomas

"Cris Hanna [SBS-MVP]" < XXXX@XXXXX.COM > wrote in message news:% XXXX@XXXXX.COM ...
You have two issues
1. SBS 2003 R2 does not contain the DFS-R bits
2. SBS 2003 does not support trusts with another domain.

So if you want DFS-R to work, you'd need another Windows Server 2003 R2 std server in your SBS domain and then the other server would have to belong to the SBS domain.

OR you can run the transition pack on your SBS server and change it to a standard server and then you can support trusts and DFS-R

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"VanBC" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM ...
Hello,

We have a Windows Sever 2003 R2 Standard Edition SP2(hostname is Mars)
running on Intel Core2 Quad CPU Q6600 @2.4GHz and a Windows Sever 2003 for
Small Business Server SP2(hostname is Doublehelix) running on Dual Core AMD
Opteron Processor 270 @ 2.01GHz. They are on the same sub-network but in
different locations and domains(lakescom.net & blcomfor.local). Each of them
is a domain computer of the other one. Doublehelix has most of our important
data, applications and MSSQL services only.

A fault tolerance/disaster recovery solution is necessary for us. If
Doublehelix goes down, users can still access data and run programs on Mars.

First, we created DFS roots and linked them to share folders on both
servers, and then tried DFS replication group for data collection on Mars but
failed. The error said oublehelix.lakescom.net: the service control manager
cannot be opened. Access is denied We are not sure if the reason is, that
not all new functionality (snap in's) are showing after doublehelix upgraded
to SBS R2, specifically the DFS management console.
Could you please tell me what would cause this problem?

In our case, is the DFS replication possible and enough for us?
If so, how can we implement it?
Does one domain have to be removed?
Do we need to upgrade one or both servers? If so, which edition (2003
Enterprise/2008)?
Is Severs-Cluster or High-Availability system applicable and necessary?
Any other solution available?

Thanks,


!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//E>">< < < < < < < Chris... man you read to fast.... he does not have
2 sbs machines, one is Windows 2003 R2 the other SBS 2003 SP2 and the Windows
2003 R2 is setup as a domain controlle<.< &nbs<;< Dirk-Thom<s< <
 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by Cris Hanna » Fri, 11 Jul 2008 06:25:36

his is a multi-part message in MIME format.


He says they're in different domains.

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"Dirk-Thomas Brown" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM ...
Chris... man you read to fast.... he does not have 2 sbs machines, one is Windows 2003 R2 the other SBS 2003 SP2 and the Windows 2003 R2 is setup as a domain controller.

Dirk-Thomas

"Cris Hanna [SBS-MVP]" < XXXX@XXXXX.COM > wrote in message news:% XXXX@XXXXX.COM ...
You have two issues
1. SBS 2003 R2 does not contain the DFS-R bits
2. SBS 2003 does not support trusts with another domain.

So if you want DFS-R to work, you'd need another Windows Server 2003 R2 std server in your SBS domain and then the other server would have to belong to the SBS domain.

OR you can run the transition pack on your SBS server and change it to a standard server and then you can support trusts and DFS-R

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"VanBC" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM ...
Hello,

We have a Windows Sever 2003 R2 Standard Edition SP2(hostname is Mars)
running on Intel Core2 Quad CPU Q6600 @2.4GHz and a Windows Sever 2003 for
Small Business Server SP2(hostname is Doublehelix) running on Dual Core AMD
Opteron Processor 270 @ 2.01GHz. They are on the same sub-network but in
different locations and domains(lakescom.net & blcomfor.local). Each of them
is a domain computer of the other one. Doublehelix has most of our important
data, applications and MSSQL services only.

A fault tolerance/disaster recovery solution is necessary for us. If
Doublehelix goes down, users can still access data and run programs on Mars.

First, we created DFS roots and linked them to share folders on both
servers, and then tried DFS replication group for data collection on Mars but
failed. The error said oublehelix.lakescom.net: the service control manager
cannot be opened. Access is denied We are not sure if the reason is, that
not all new functionality (snap in's) are showing after doublehelix upgraded
to SBS R2, specifically the DFS management console.
Could you please tell me what would cause this problem?

In our case, is the DFS replication possible and enough for us?
If so, how can we implement it?
Does one domain have to be removed?
Do we need to upgrade one or both servers? If so, which edition (2003
Enterprise/2008)?
Is Severs-Cluster or High-Availability system applicable and necessary?
Any other solution available?

Thanks,


!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//E>">< < < <
 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by Dirk-Thoma » Fri, 11 Jul 2008 06:48:32

his is a multi-part message in MIME format.


Looks like its me whom reads to fast! :(

Sorry..
"Cris Hanna [SBS-MVP]" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM ...
He says they're in different domains.

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"Dirk-Thomas Brown" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM ...
Chris... man you read to fast.... he does not have 2 sbs machines, one is Windows 2003 R2 the other SBS 2003 SP2 and the Windows 2003 R2 is setup as a domain controller.

Dirk-Thomas

"Cris Hanna [SBS-MVP]" < XXXX@XXXXX.COM > wrote in message news:% XXXX@XXXXX.COM ...
You have two issues
1. SBS 2003 R2 does not contain the DFS-R bits
2. SBS 2003 does not support trusts with another domain.

So if you want DFS-R to work, you'd need another Windows Server 2003 R2 std server in your SBS domain and then the other server would have to belong to the SBS domain.

OR you can run the transition pack on your SBS server and change it to a standard server and then you can support trusts and DFS-R

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues

"VanBC" < XXXX@XXXXX.COM > wrote in message news: XXXX@XXXXX.COM ...
Hello,

We have a Windows Sever 2003 R2 Standard Edition SP2(hostname is Mars)
running on Intel Core2 Quad CPU Q6600 @2.4GHz and a Windows Sever 2003 for
Small Business Server SP2(hostname is Doublehelix) running on Dual Core AMD
Opteron Processor 270 @ 2.01GHz. They are on the same sub-network but in
different locations and domains(lakescom.net & blcomfor.local). Each of them
is a domain computer of the other one. Doublehelix has most of our important
data, applications and MSSQL services only.

A fault tolerance/disaster recovery solution is necessary for us. If
Doublehelix goes down, users can still access data and run programs on Mars.

First, we created DFS roots and linked them to share folders on both
servers, and then tried DFS replication group for data collection on Mars but
failed. The error said oublehelix.lakescom.net: the service control manager
cannot be opened. Access is denied We are not sure if the reason is, that
not all new functionality (snap in's) are showing after doublehelix upgraded
to SBS R2, specifically the DFS management console.
Could you please tell me what would cause this problem?

In our case, is the DFS replication possible and enough for us?
If so, how can we implement it?
Does one domain have to be removed?
Do we need to upgrade one or both servers? If so, which edition (2003
Enterprise/2008)?
Is Severs-Cluster or High-Availability system applicable and necessary?
Any other solution available?

Thanks,


 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by SuperGumby » Fri, 11 Jul 2008 06:54:52

He says they are in different domains, but he also suggests that each is a
DC in the other's domain, an impossible situation.


"Cris Hanna [SBS-MVP]" < XXXX@XXXXX.COM > wrote in

He says they're in different domains.

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues



Chris... man you read to fast.... he does not have 2 sbs machines, one is
Windows 2003 R2 the other SBS 2003 SP2 and the Windows 2003 R2 is setup as a
domain controller.

Dirk-Thomas

"Cris Hanna [SBS-MVP]" < XXXX@XXXXX.COM > wrote in

You have two issues
1. SBS 2003 R2 does not contain the DFS-R bits
2. SBS 2003 does not support trusts with another domain.

So if you want DFS-R to work, you'd need another Windows Server 2003 R2
std server in your SBS domain and then the other server would have to belong
to the SBS domain.

OR you can run the transition pack on your SBS server and change it to a
standard server and then you can support trusts and DFS-R

--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues



Hello,

We have a Windows Sever 2003 R2 Standard Edition SP2(hostname is Mars)
running on Intel Core2 Quad CPU Q6600 @2.4GHz and a Windows Sever 2003
for
Small Business Server SP2(hostname is Doublehelix) running on Dual
Core AMD
Opteron Processor 270 @ 2.01GHz. They are on the same sub-network but
in
different locations and domains(lakescom.net & blcomfor.local). Each
of them
is a domain computer of the other one. Doublehelix has most of our
important
data, applications and MSSQL services only.

A fault tolerance/disaster recovery solution is necessary for us. If
Doublehelix goes down, users can still access data and run programs on
Mars.

First, we created DFS roots and linked them to share folders on both
servers, and then tried DFS replication group for data collection on
Mars but
failed. The error said "Doublehelix.lakescom.net: the service control
manager
cannot be opened. Access is denied". We are not sure if the reason is,
that
not all new functionality (snap in's) are showing after doublehelix
upgraded
to SBS R2, specifically the DFS management console.
Could you please tell me what would cause this problem?

In our case, is the DFS replication possible and enough for us?
If so, how can we implement it?
Does one domain have to be removed?
Do we need to upgrade one or both servers? If so, which edition (2003
Enterprise/2008)?
Is Severs-Cluster or High-Availability system applicable and
necessary?
Any other solution available?

Thanks,
 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by Cris Hanna » Fri, 11 Jul 2008 12:05:20

up saw that too

--
Cris Hanna [SBS - MVP]
------------------------------------
MVPs do not work for Microsoft
Please do not submit questions directly to me.
"SuperGumby [SBS MVP]" < XXXX@XXXXX.COM > wrote in message
news:ON% XXXX@XXXXX.COM ...

 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by VmFuQk » Sat, 12 Jul 2008 01:12:00

i Cris & SuperGumby,

Each of my two servers is a domain/client computer, not a DC of the other one.
How can I run the transition pack on the SBS server and change it to a
standard server? After that, do I have to reset all DCs, ADs, users, other
computers, etc.

Thanks,

"Cris Hanna [SBS - MVP]" wrote:

 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by SuperGumby » Sat, 12 Jul 2008 08:15:46

BS _must_ be a DC.
A DC _cannot_ be a client of another domain. (In some ways a 'trust' may be
seen as such a relationship but it's more like brother/sister than
parent/child)

I think you are confusing 'Windows AD Domain' and 'Internet Domain', two
distinct items.

I would _possibly_ make the non-SBS a 2nd DC in the SBS AD domain. However,
it sounds like you are using the 2nd server as a web server. It is therefore
better not to make it part of the domain. Stuff DFS, throw an FTP server on
the web server and sync files by FTP.

"VanBC" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...


 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by VanB » Wed, 16 Jul 2008 02:23:38


Hello,

We have a Windows Sever 2003 R2 Standard Edition SP2(hostname is Mars)

running on Intel Core2 Quad CPU Q6600 @2.4GHz and a Windows Sever 2003
for Small Business Server SP2(hostname is Doublehelix) running on Dual
Core AMD Opteron Processor 270 @ 2.01GHz. They are on the same
sub-network but in different locations and domains(lakescom.net &
blcomfor.local). Doublehelix has most of our important data,
applications and MSSQL services only.

A fault tolerance/disaster recovery solution is necessary for us. If
Doublehelix goes down, users can still access data and run programs on
Mars.

First, we created DFS roots and linked them to share folders on both
servers, and then tried DFS replication group for data collection on
Mars but
failed. The error said oublehelix.lakescom.net: the service control
manager
cannot be opened. Access is denied We are not sure if the reason is,
that
not all new functionality (snap in's) are showing after doublehelix
upgraded
to SBS R2, specifically the DFS management console.
What would cause this problem?

In our case, is the DFS replication possible and enough for us?
If so, how can we implement it?
Does one domain have to be removed?
Do we need to upgrade one or both servers? If so, which edition (2003
Enterprise/2008)?
Is Severs-Cluster or High-Availability system applicable and necessary?

Any other solution available?

Thanks,


--
VanBC
------------------------------------------------------------------------
VanBC's Profile: http://www.yqcomputer.com/
View this thread: http://www.yqcomputer.com/

http://www.yqcomputer.com/
 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by v-milel » Wed, 16 Jul 2008 19:55:45

ello,

Thank you for your post.

Please allow me to confirm that my understandings are correct. As I
understand it, the issue is:

You want to enable the fault tolerance on the important data on the
Doublehelix (Windows SBS 2003 SP2). You need the assistant on the DFS
creation and best practice for the fault tolerance implement.

If I have misunderstood your concerns please feel free to let me know.

Suggestion:
=========================
It should be expected that you will encounter the error when you attempt to
create replication group between the Windows Server 2003 R2 and Windows SBS
2003 because SBS server do not have DFS-R (DFS replication) function even
when SBS server is upgraded to R2. This means that you can create DFS
namespace without the replication between them.

Several factors to implement DFS with DFS-R:

1. SBS server can be migrated to the Windows Server 2003 R2 or Windows
Server 2008.

Neither DFS-R nor server cluster is supported on the Windows SBS server.
You have to migrate the SBS server to a Windows Server before you can DFS-R
and server cluster.

2. The DF-R must happen on one forest, or two forests with trust.

As we know the SBS does not support trust, so lakescom.net and
blcomfor.local must be in separated forests without the trust. However,
replication groups cannot span across different forests.

Which kind of disaster recovery options that you should choose is actually
depend on your requirement such as:

- What application needs high availability?
- How long you can tolerate for an application to be out of service?
- How many technical and finance resources that you could put to provide
high availability?

If you only want the data redundancy on the SBS server, you can simply
create RAID on the SBS server for accidently single disk failure. If you
can tolerate very short period of downtime and the applications are
compatible with Windows Server cluster, you may consider server cluster and
use shared storage. Otherwise, if it is acceptable to spend some time to
install a server and restore the data to perform disaster recovery, server
cluster is unnecessary. To increase availability of data, load sharing and
simplified data migration, you can count on the DFS (Distributed File
System) with DFS-R.

=========================
For more information regarding Windows fault tolerance and DFS:
Strategies for Fault-Tolerant Computing
http://www.microsoft.com/windowsserver2003/evaluation/performance/faulttoler
ance.mspx

Designing and Deploying File Servers
http://technet2.microsoft.com/windowsserver/en/library/42befce4-7c15-4306-8e
dc-a80b8c57c67d1033.mspx?mfr=true

Distributed File System (DFS)
http://technet2.microsoft.com/windowsserver/en/library/370f16f9-dd08-45dc-8c
f2-d9e2bfeada881033.mspx?mfr=true

Best practices for Distributed File System (DFS)
http://technet2.microsoft.com/WindowsServer/en/Library/007e4e66-af67-4bfe-bf
70-780412aeed6f1033.mspx?mfr=true

If you have any questions or concerns, please do not hesitate to let me
know.



Sincerely,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=================================================
 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by Steve Fost » Wed, 16 Jul 2008 20:11:56


At the very least, having two domains makes no sense whatsoever. I'd start
by losing the Mars domain, and moving that server into the SBS domain.

Then you can try setting up DFS, and see if it does what you need.

Having a second server doesn't generally add anything useful in terms of
"system availability". It's all very well having a network share available
even if the SBS is down, but you won't have email, nor remote access, nor
Companyweb, nor SQL, and so on and so on. In practical terms, it's usually
better to spend more on the SBS such that it's less likely to be
unavailable in the first place (ie RAID, redundant PSU, good h/w warranty)
than to buy a second server that's never going to be a "silver bullet".

Guaranteeing uptime is a serious business, and costs serious money.

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.
 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by VanB » Thu, 17 Jul 2008 01:41:43


Hi Miles & Steve,

We do have RAID on our SBS, but can't tolerate more than 1/2 hour
downtime to replace mother board, inside power supply, etc.

Can I reset the R2 server as the 2nd DC in the SBS domain and do one
way DFS replication(SBS->R2).

Thanks for your help,

Peter Luo


--
VanBC
------------------------------------------------------------------------
VanBC's Profile: http://www.yqcomputer.com/
View this thread: http://www.yqcomputer.com/

http://www.yqcomputer.com/
 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by Steve Fost » Thu, 17 Jul 2008 05:38:23


See the first two paragraphs of my original response.

Note that in my experience, DFS (at least pre the Server R2 enhancements
that you can't use) does not work well in environments where there is
heavy editing of the files that live in the DFS share(s).

A small business that cannot tolerate >30 minutes of downtime? Really?
*Everything* relies on the SBS? How did the business function pre-SBS?

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.
 
 
 

DFS replication between Windows Sever 2003 R2 & SBS

Post by v-milel » Thu, 17 Jul 2008 20:40:58


Hello Peter,

As I mentioned in my last post, the DFS replication (DFS-R) is not
supported on the SBS 2003 R2.

However, you can set up the DFS with the FRS (File Replication Service) for
the replication between SBS 2003 server and Windows Server 2003. However,
new features such as Remote differential compression (RDC) don't contained
in the FRS.

Monitoring and Troubleshooting the File Replication Service
http://www.yqcomputer.com/
s.mspx

Distributed File System Technology Center
http://www.yqcomputer.com/
mspx

Hope this helps. Also, if you have any questions or concerns, please do not
hesitate to let me know.

Sincerely,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.