Eugene
Sun Aug 05 13:29:07 CDT 2007
hi Anver,
You have several new questions, and I'll just answer them each in one
paragraph.
To join to a new domain, you can either login to own PC domain which
is a workgroup, or 'disconnect' by changing membership of domain to
a workgroup, reboot then login to the workgroup and then use
ConnectComputer to the new SBS domain.
Emails: if I understand you correctly, you want PC clients to download
email directly to their own .PST file. Is there a reason for this, e.g. are
PCs mostly notebooks?
If not, I recommend using Exchange and using SMTP to directly receive
the email if possible, combining with a DDNS service if not using static
public IP for the server/router.
If not using direct SMTP, I'd still recommend using Exchange with POP
Connector to download the email. This is because your customer will be
missing a strong benefit of having a server to manage the emails.
PST are local on the PCs which can get corrupted or lost, not as robust
as Exchange database. With roaming profiles, you have flexibility to
access emails from any PC. And with remote access, users can access
their emails on the server. Users can still have a local email cache that
is autosync with Exchange, called an OST.
I would also examine whether it is suitable or possible to reconfigure
the service provided by the ISP as managing many POP Connector
users can be a pain. I use direct SMTP to Exchange whenever possible,
and use ISP with a catch-all email account to serve as a Gloabl POP
account, which acts as the backup MX. So email goes to the ISP
only when the server is down or unavailable (for DDNS).
SCS personal firewall should not be confused with ISA client FW.
The ISA is a network and app FW which is filtering at the network
level, based on policies decides which traffic gets out or not, such
as whether a PC should be sending SMTP out (like malware do)
or whether only allowed SMTP within the LAN, while Exchange
is allowed to speak SMTP past the ISA FW.
The ISA FW client is designed to work with ISA; one of the things
it does is compress IP traffic between PC and ISA and also provides
the mechanism to auto-authentication with ISA, but it doesn't do the
type of filtering that a personal FW does.
SCS filtering occurs before ISA client, which essentially transports the
TCP traffic to ISA FW. So yes, you'd install both.
HTH,
Eugene Tan
SBS MVP
=========================
"Anver" <Anver@discussions.microsoft.com> wrote in message
news:CD0DD239-2AF6-47D6-8F02-ABE99F04C40C@microsoft.com...
> Hi Eugene Tan,
>
> Thanks for the reply, but still I need to disconnect all the client pcs(I
> mean now client pcs are connected SBS2000, so disconnect from the existing
> server and join to new server) - correct?
> Also please note that, we have ISP based POP mails, we would like to use
> Exchange - only for the internal distribution and the mails direcly will
> deliver to the clients pc (local pst file).
> We have existing Symantec client security for the clients, and we may add
> ISA2004(as part of the SBS2003 premium), If we install the ISA2004 and
> this
> will also install the ISAclient on the client's pc - do you recommend both
> security
> Symantec client security and ISA client on client's pc?
> Which is a better firewall? - a Hardware firewall(we have pix 506) or
> ISA2004? do we need both?
>
> kindly advise
> Rgds
> Anver
> "Eugene Tan" wrote:
>
>> hi Anver,
>>
>> Sorry didn't see your reply earlier.
>>
>> For the client PCs: after you complete setting up SBS2k3, you simply
>> need to join the PCs to the new SBS2k3R2 domain, by following the
>> instructions on how to connectcomputer. You will do this via IE on
>> the PC clients and it's straight forward.
>>
>> If you plan to assign any users as local admins on the PCs, then you'll
>> need to create these user accounts on the SBS first.
>>
>> HTH,
>> Eugene Tan
>> SBS MVP
>>
>> ==============================
>> "Anver" <Anver@discussions.microsoft.com> wrote in message
>> news:21FE157B-C05C-4C39-8C2F-6A95B0BECCD0@microsoft.com...
>> > Ok, now understood as OEMSBS2000 and the related licenses cannot be
>> > upgraded
>> > from one box to another box to SBS2003R2.
>> > So we planned as buy new box with sbs2003 R2 and reconfigure all the
>> > client
>> > pcs.
>> > My plan for the client pcs are: disconnect the client pcs from the
>> > current
>> > serverbox and reconfigure the client pc for the newsbs2003box.
>> >
>> > any comments for clients pcs?
>> > Please advise
>> >
>> > Rgds
>> > Anver
>> >
>> >
>> >
>> >
>> > "Eugene Tan" wrote:
>> >
>> >> hi Anver,
>> >>
>> >> The info you provide is a bit unclear, but if you are asking a
>> >> licensing
>> >> question,
>> >> the answer is no, you can't transfer an OEM license from one box to
>> >> another.
>> >>
>> >> So you can't transfer SBS2k OEM to the new box as the basis to upgrade
>> >> to SBS2k3 R2. Even if you upgraded to SBS2k3 on the old box, you
>> >> can't
>> >> transfer this to another box unless the replacement box has its own
>> >> qualifying
>> >> license, such as SBS2k3 or another SBS2k.
>> >>
>> >> HTH,
>> >> Eugene Tan
>> >> SBS MVP
>> >>
>> >> ==========================
>> >> "Anver" <Anver@discussions.microsoft.com> wrote in message
>> >> news:B62C7948-4098-4310-80D3-20D8B3321BCA@microsoft.com...
>> >> > Hi,
>> >> >
>> >> > I have OEM SBS2000 - my concern is that can I upgrade this to OEM
>> >> > SBS2003
>> >> > R2
>> >> > in to a different server PC(I would like to change the existing
>> >> > server
>> >> > PC)
>> >> >
>> >> > (I will buy a new Server PC plus the upgrade version of SBS2003 R2 -
>> >> > is
>> >> > that
>> >> > possible?)
>> >> > Kindly advise
>> >> >
>> >> > Rgds
>> >>
>> >>
>> >>
>>
>>
>>