Outlook by the sound : SBS03_Tips

Need Help Diagnosing Spam Source

OBTS — Sat, 11 Oct 2008 22:39:22 GMT

From: "Richard K"
Subject: Need Help Diagnosing Spam Source
Date: Fri, 3 Oct 2008 10:17:57 -0400
Newsgroups: microsoft.public.windows.server.sbs

SBS 2003 Std. server (call him Company1) with Windows XP clients
Trend Micro WFBS on network

I have been working on an issue with spam mail that is causing RBL issues.
At first I was thinking it was a virus somewhere in the network either using
Company1 Exchange as the sourcing to send these spam mails or the XP client
himself was sending port 25 traffic. Now I'm thinking I may have an open
relay where some outside source is using the Company1 Exchange to send the
mails. I have found an example which helps explain my thoughts.

1. I look in the Company1 Exchange MTS for any messages I see for a period
of time. I see TONS of messages which tells me it is the Company1 Exchange
box sending the messages and not some rougue XP client
2. I started receiving some more spam to my email address in my office SBS
(Company2) These messages were intended for an email address at Company1
that I have a forward on to my server at Company2
3. I have found a specific message that is in the Company1 MTS AND that I
received via the forward so I can match up that the email did originate from
the Company1 SBS server.
4. When I look at the details of the message in the Company1 MTS the
"Sender" is not anyone on the network ("dolore-'riclite@palpilot.com.tw")
5. I have attached the Internet Headers of this message that I get in my
Outlook. This message was not caught by the AV.

Q1 - How are these messages getting into the Exchange queue of the Comany1
SBS? From an client machine or am I missing some type of authentication
and/or have a relay open and something is using the Company1 Exchange server
as its engine?
Q2 - What do I need to do to make sure only valid users on the Company1
network may send emails via the Company1 Exchange and that I don't have any
relay issues?

Thanks!

-Richard K

Microsoft Mail Internet Headers Version 2.0

Received: from vms172071pub.verizon.net ([206.46.172.71]) by foxdtechllc.com
with Microsoft SMTPSVC(6.0.3790.1830);
Wed, 1 Oct 2008 05:18:20 -0400
Return-path: dolore-'riclite@palpilot.com.tw
Received: from fergusontrenching.com ([151.196.94.114])

by vms172071.mailsrvcs.net
(Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006))
with ESMTPA id <0K810057WZ6JTXJ3@vms172071.mailsrvcs.net> for
rkokoski@foxdtechllc.com; Wed, 01 Oct 2008 04:18:19 -0500 (CDT)

Received: from [125.131.129.1] ([125.131.129.1]) by fergusontrenching.com
with
Microsoft SMTPSVC(6.0.3790.3959); Wed, 01 Oct 2008 05:18:17 -0400
Date: Wed, 01 Oct 2008 18:18:16 +0900
From: dolore <dolore-'riclite@palpilot.com.tw>
Subject: Warning
To: <postmaster@fergusontrenching.com>
Message-id: <000b01c923a6$a340b540$0181837d@APSEODESKBHPARK>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-type: multipart/alternative;
boundary="----=_NextPart_000_000C_01C923F2.13285D40"
Content-class: urn:content-classes:message
Thread-topic: Warning
Thread-index: Ackj8hMocknXUw0QSHGI/D/CTZsDJA==
X-MS-TNEF-Correlator:
X-TM-AS-Product-Ver: SMEX-8.1.0.1092-5.500.1027-16190.006
X-TM-AS-Result: Yes-43.210500-5.000000-31
X-TM-AS-User-Approved-Sender: No
X-TM-AS-User-Blocked-Sender: No
X-OriginalArrivalTime: 01 Oct 2008 09:18:17.0787 (UTC)
FILETIME=[A3E2E8B0:01C923A6]
------=_NextPart_000_000C_01C923F2.13285D40
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
------=_NextPart_000_000C_01C923F2.13285D40
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
------=_NextPart_000_000C_01C923F2.13285D40-

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

From: "Lanwench [MVP - Exchange]"
Date: Fri, 3 Oct 2008 11:11:04 -0400

Richard K wrote:
> SBS 2003 Std. server (call him Company1) with Windows XP clients
> Trend Micro WFBS on network
>
> I have been working on an issue with spam mail that is causing RBL
> issues.

What do you mean by RBL issues?

> At first I was thinking it was a virus somewhere in the
> network either using Company1 Exchange as the sourcing to send these
> spam mails or the XP client himself was sending port 25 traffic.

You can block your clients from accessing the Internet on anything besides
80 & 443. That's not a bad plan in general....do this in ISA or your
perimeter firewall.

> Now
> I'm thinking I may have an open relay where some outside source is
> using the Company1 Exchange to send the mails.

Unlikely, unless you specifically enabled that. Exchange does not permit
open relay out of the box. It permits authenticated relay, which I generally
disable unless absolutely necessary - but if you have a good password policy
you shouldn't worry about that overmuch. .

> I have found an
> example which helps explain my thoughts.
> 1. I look in the Company1 Exchange MTS for any messages I see for a
> period of time. I see TONS of messages which tells me it is the
> Company1 Exchange box sending the messages and not some rougue XP
> client

Well, it's sending *messages* - including NDRs to spammers who tried to send
*you* their junk. This doesn't demonstrate spammers are relaying through
your server.

> 2. I started receiving some more spam to my email address in my
> office SBS (Company2) These messages were intended for an email
> address at Company1 that I have a forward on to my server at Company2

OK - not sure what that demonstrates.

> 3. I have found a specific message that is in the Company1 MTS AND
> that I received via the forward so I can match up that the email did
> originate from the Company1 SBS server.

Well - you demonstrated that it was mail sent to your address at
company1 -not that it *originated* there. Did you look at the headers?

> 4. When I look at the details of the message in the Company1 MTS the
> "Sender" is not anyone on the network
> (dolore-'riclite@palpilot.com.tw)

Right. Because the sender is a spammer. The spammer sent mail *to* you - not
*through* you.

> 5. I have attached the Internet Headers of this message that I get
> in my Outlook. This message was not caught by the AV.

Sure, why would it be, unless it had a virus-laden or otherwise bad
attachment?
>
> Q1 - How are these messages getting into the Exchange queue of the
> Comany1 SBS? From an client machine or am I missing some type of
> authentication and/or have a relay open and something is using the
> Company1 Exchange server as its engine?

You're just getting spam. You aren't creating it.

> Q2 - What do I need to do to make sure only valid users on the
> Company1 network may send emails via the Company1 Exchange and that I
> don't have any relay issues?

Look in your virtual SMTP server properties, relay settings. But it's that
way now, I promise, unless you deliberately changed it.

See http://www.msexchange.org/tutorials/MF005.html for a good overview of
relaying and spam.
>
> Thanks!

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

From: "Richard K"
Date: Fri, 3 Oct 2008 11:58:56 -0400

RBL issues - The external IP address (151.196.94.114) is listed in various
RBLs include CBL and Spamhaus. We thought we have cleaned the network of
any issues (according to the latest TM WFBS reports we are clean) but then
the IP gets put back on the RBL again as a spam sourcer. This is the
primary reason for this thread along with some other thread questions I have
had. I am having trouble identify the culprit.

This is SBS 2003 std so no ISA. The SBS has a dual nic set up and the XP
clients must go through the server to get outside.

I looked at your link on possible relays and I believe you are correct about
the relay in the case. All appears set up correctly

I see your point about the NDRs now and it makes sense. In the example I
included (internet header) as I read it: it is coming from
"dolore-'riclite@palpilot.com.tw" being sent to
"postmaster@fergusontrenching.com" The "postmaster" address is just another
SMTP address attached to the administrator account. That same administrator
account has a forward set up to my email address (rkokoski@foxdtechllc.com),
hence that is how I ultimately get the spam.

Bottom line Lanwrench... I'm just trying to figure out how the IP address is
consistently reappearing on the RBL lists and I'm kind of stuck. This
server is also being bombarded with incoming spam mail and I am looking at
options to have email first "cleaned" to cut down on the amount of incoming
spam mail that may reach the server for it to then have to process in some
form.

Thanks for any assistance and guidance!

-Richard K

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

From: "Lanwench [MVP - Exchange]"
Date: Fri, 3 Oct 2008 12:30:19 -0400

Richard K <rkokoski@foxdtechllc.com> wrote:
> RBL issues - The external IP address (151.196.94.114) is listed in
> various RBLs include CBL and Spamhaus.

Ah, you mean you've been blacklisted. The blacklisting should explain why.
Do you send out a lot of mass mailings?

What antivirus/workstation security software do you run?

> We thought we have cleaned
> the network of any issues (according to the latest TM WFBS reports we
> are clean) but then the IP gets put back on the RBL again as a spam
> sourcer. This is the primary reason for this thread along with some
> other thread questions I have had. I am having trouble identify the
> culprit.
> This is SBS 2003 std so no ISA. The SBS has a dual nic set up and
> the XP clients must go through the server to get outside.

Do you use a good perimeter firewall appliance? I don't like the two-NIC
setup unless you've got Premium and use ISA. Multihomed DCs cause problems.
Your setup isn't as secure as it ought to be, either, unless you've got a
good firewall.

>
> I looked at your link on possible relays and I believe you are
> correct about the relay in the case. All appears set up correctly
>
> I see your point about the NDRs now and it makes sense. In the
> example I included (internet header) as I read it: it is coming from
> "dolore-'riclite@palpilot.com.tw" being sent to
> "postmaster@fergusontrenching.com" The "postmaster" address is just
> another SMTP address attached to the administrator account. That
> same administrator account has a forward set up to my email address
> (rkokoski@foxdtechllc.com), hence that is how I ultimately get the
> spam.
> Bottom line Lanwrench... I'm just trying to figure out how the IP
> address is consistently reappearing on the RBL lists and I'm kind of
> stuck. This server is also being bombarded with incoming spam mail
> and I am looking at options to have email first "cleaned" to cut down
> on the amount of incoming spam mail that may reach the server for it
> to then have to process in some form.

Sure. I'd check out Postini or MailFoundry or MXLogic.

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

From: RichardK
Date: Fri, 3 Oct 2008 10:28:01 -0700

We are using Trend Micro WFBS Advanced for server and XP workstions. All are
up to date. The blacklisting only indicates the IP (151.196.94.114) has been
a source of spam mails and not much else. Maybe you can see something I
cannot see for that IP.

The dual nic set up is the standard setup I employ. In this case it's what
I inherited. Between the external nic and the DSL there is a Netgear FVS318
appliance with limited incoming port openings (443, 4125, 3389, 25) but I
don't see it with much more capability. I know you mentioned possibly one
of the XP clients opening it's own port 25 and sending the spam. Am I
assuming correctly this can even be done since it would have to go through
the dual nic SBS box? In my scheme the FVS318 will only know the SBS
external NIC IP address since the XP clients are natted to a completely
different subnet off of the inside LAN nic. Without the capability of the
FVS318 to limit outbound port traffic the only thing I came across is a step
by step on how to create and AD policy to shut down port 25 to all XP clients
since none of them should be using it.

I appreciate all of your input!!

-Richard K

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

From: "Lanwench [MVP - Exchange]"
Date: Fri, 3 Oct 2008 13:42:57 -0400

Richard K wrote:
> We are using Trend Micro WFBS Advanced for server and XP workstions.

Have you run a full scan recently?

> All are up to date. The blacklisting only indicates the IP
> (151.196.94.114) has been a source of spam mails and not much else.
> Maybe you can see something I cannot see for that IP.

I just did a lookup on dnsreport.com and it's listed in several places.
>
> The dual nic set up is the standard setup I employ. In this case
> it's what I inherited. Between the external nic and the DSL there is
> a Netgear FVS318 appliance with limited incoming port openings (443,
> 4125, 3389, 25) but I don't see it with much more capability. I
> know you mentioned possibly one of the XP clients opening it's own
> port 25 and sending the spam. Am I assuming correctly this can even
> be done since it would have to go through the dual nic SBS box?

Yes.

> In
> my scheme the FVS318 will only know the SBS external NIC IP address
> since the XP clients are natted to a completely different subnet off
> of the inside LAN nic. Without the capability of the FVS318 to limit
> outbound port traffic

I think it can, but I don't know how (haven't used one of those for a
while). I'd get a better firewall appliance that can do this for you. Your
workstations shouldn't need to access the Internet on anything other than 80
or 443 for most purposes.

> the only thing I came across is a step by step
> on how to create and AD policy to shut down port 25 to all XP clients
> since none of them should be using it.

I wouldn't do it this way.
>
> I appreciate all of your input!!

What about mass mailings? Does this client do a lot?

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

From: RichardK
Date: Fri, 3 Oct 2008 11:32:14 -0700

I am running full scans every night until I get this problem solved. Hence
the "clean" reports I get every morning. I know it's listed in several
places with CBL and spamhaus the ones I am really paying attention to.

the ports open are 25,44,3389, 4125 for all INCOMING traffic. I cannot find
anywhere on that appliance to control outbound traffic ports. I use 3389 to
RDP directly to the server and 4125 for RWW. I have not applied the GP for
the port 25 shutdown but without the right hardware I'm limited in my options
right now. This client does not do alot of mass mailings but indirectly I
think they are doing them with some bot causing the problems. I just have
not found it yet.

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

Date: Fri, 03 Oct 2008 19:35:35 +0100
From: stephen

Richard K wrote:
> We are using Trend Micro WFBS Advanced for server and XP workstions. All are
> up to date. The blacklisting only indicates the IP (151.196.94.114) has been
> a source of spam mails and not much else. Maybe you can see something I
> cannot see for that IP.

You mentioned that you would like your mail pre-filtered. WFBS Advanced
allows you to set up the Trend Interscan Messaging Hosted Security
service which is a free malware scanning service. You can register for
the service at the Trend site. You basically change your MX to point to
their server and tell them your server's IP. It's a half-decent system,
but my major gripe is that they don't permit messages > 10MB on the
basic, free service and silently discard them (no NDR to sender).

http://cbl.abuseat.org/lookup.cgi?ip=151.196.94.114&.submit=Lookup

says that you are infected with a spam bot. I would change that SBS to a
one nic and block and log port 25 at the firewall from everything bar
SBS. The cuprit workstation will soon be revealed from the logged denials.

Failing that, install a network monitoring tool on your server and
examine the internal nic traffic to find the rogue PC. Ethereal or the
Microsoft Network monitor will do the trick.

Also make sure you have recipient filtering in Exchange to stop you
sending backscatter.

Install and run a quick scan of MalwareBytes anti-malware on every
workstation. It will find a fix stuff that Trend doesn't.

--
stephen

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

From: RichardK
Date: Fri, 3 Oct 2008 11:59:01 -0700

I know about the TM WFBS service but I have not set it up yet and tested. I
did not know about the 10MB limit but glad I found that out. I'm surprise
their default action would not be to just send it on it's way vs. reject with
no NDR.

I do see in the netgear appliance where I can block specific outbound ports
based on LAN address. I am thinking this obviosly won't work with the dual
nic since the WAN and LANs are on the seperate subnets or can I (10.0.16.x
WAN and 10.0.0.x LAN). I am thinking if I specify anything in the 10.0.0.x
range the router does not see that address since it's natted. Out of
curiousity.... I have always seen the preaching of using a dual nic model for
the SBS. What's with the single nic design "being better"?

Can you please explain more about "Also make sure you have recipient
filtering in Exchange to stop you sending backscatter." I'm not sure what
you are referring to here.

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

From: "SteveB"
Date: Fri, 3 Oct 2008 12:20:17 -0700

There has always been a debate about dual NICs on SBS. I have always
preferred that along with ISA for my clients, but again others are adamantly
against that configuration. It now becomes a moot point with SBS 2008 (based
on Windows Server 2008) where you can no longer have dual NICs at all.

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

Date: Fri, 03 Oct 2008 20:26:14 +0100
From: Stephen

Richard K wrote:
> I know about the TM WFBS service but I have not set it up yet and tested. I
> did not know about the 10MB limit but glad I found that out. I'm surprise
> their default action would not be to just send it on it's way vs. reject with
> no NDR.

I complained about that to Trend. It makes it unusable in my book. Shame
really, because it's a decent system for the money! I personally use
MailScanner on an external server to prefilter my mail (and our clients).

>
> I do see in the netgear appliance where I can block specific outbound ports
> based on LAN address. I am thinking this obviosly won't work with the dual
> nic since the WAN and LANs are on the seperate subnets or can I (10.0.16.x
> WAN and 10.0.0.x LAN). I am thinking if I specify anything in the 10.0.0.x
> range the router does not see that address since it's natted. Out of
> curiousity.... I have always seen the preaching of using a dual nic model for
> the SBS. What's with the single nic design "being better"?

Yes, I'm not sure if the Netgear does egress filtering. If not, it's not
much of a firewall appliance. If you're handy with Linux or BSD you can
set up your own firewall on an old PC with 2 nics, or install one of the
opensource firewall products on it. Personally, I use OpenBSD pf in
bridge mode so filter my traffic.

The problem with the dual nic setup is that your SBS box is performing
NAT for your workstations so your firewall sees all outbound traffic
with the SBS IP address. You can't therefore block workstations at the
firewall. I'm not all that familar with the SBS RRAS firewall in the
standard dual nic setup, but you may be able to do something there.

> Can you please explain more about "Also make sure you have recipient
> filtering in Exchange to stop you sending backscatter." I'm not sure what
> you are referring to here.

If this is not on, then exchange accepts all mail and then sends an NDR
if the recipient address doesn't exist on your server to the apparent
sender address, which can be forged. This is backscatter and spammers
can exploit it to get your server to send out spammy NDRs to arbitrary
victim address. With recipient filtering on, a message to a non-existent
address is rejected at the SMTP stage so the responsibily for the NDR
lies with the sending server, not yours. There are 2 places to check
this setting in exchange: properties of message delivery in global
settings and in the smtp virtual server advanced IP settings.

--
stephen

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

From: "Lanwench [MVP - Exchange]"
Date: Fri, 3 Oct 2008 15:21:58 -0400

Richard K wrote:
> I know about the TM WFBS service but I have not set it up yet and
> tested. I did not know about the 10MB limit but glad I found that
> out. I'm surprise their default action would not be to just send it
> on it's way vs. reject with no NDR.

Yep - agreed. I hadn't known that either. I would check out MailFoundry. If
you have fewer than 10 addresses, they won't charge for their hosted
service.
>
> I do see in the netgear appliance where I can block specific outbound
> ports based on LAN address.

You need to block all, allow some.

> I am thinking this obviosly won't work
> with the dual nic since the WAN and LANs are on the seperate subnets
> or can I (10.0.16.x WAN and 10.0.0.x LAN). I am thinking if I
> specify anything in the 10.0.0.x range the router does not see that
> address since it's natted. Out of curiousity.... I have always seen
> the preaching of using a dual nic model for the SBS. What's with the
> single nic design "being better"?

Outside of SBSland a multhomed DC is a real no-no. It isn't giving you much
in the way of security, and is making life more complex. It isn't even
supported in SBS2008, to the best of my knowledge.
>
>
> Can you please explain more about "Also make sure you have recipient
> filtering in Exchange to stop you sending backscatter." I'm not sure
> what you are referring to here.

Enable recipient filtering in Exchange system Manager - filter on recipients
not in the directory, etc.

http://www.msexchange.org/tutorials/Sender-Recipient-Filtering.html

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

From: "Gregg Hill"
Date: Sat, 4 Oct 2008 00:55:27 -0700

Richard,

Search MS knowledge base for "reverse ndr" attack, make sure you are
protected, including tarpitting, then read on.

Others have recommended blocking port 25 from workstations, and you already
have the tool for it...the WFBS client firewall.

Create a new group on the Security Settings tab (do NOT import settings),
call it Firewalled Workstations, enable the client firewall in advanced
mode, set it to High so inbound/outbound traffic is blocked except for the
exception list, then delete the exception for the SMTP port. Enable the
error message pop-up, add exceptions for normal network traffic (mine popped
errors and required exceptions for port 123 for the time service; 161 and
427 to a networked HP Laserjet 3055; 135 to my SBS; and oddly enough, port
137 that is already on the exception list; port 1025; ICMP protocol). I got
tired of seeing the popup while typing this message, so I just exempted the
range from 1000 to 65535. Yes, it's overkill, but I was just testing it to
see if it would suit your needs.

To test it, go to a workstation and use Telnet on port 25 to an outside mail
server, for example, "telnet mail.microsoft.com 25" (but preferably to one
you control).You should get the server's mail greeting. Type "quit" to kill
the telnet session, then move that workstation into the new Firewalled
Workstations group. It only
takes about a minute or two for the workstation to get the new settings.
Retest with Telnet, and it should fail.

Now look at the reports on the server...oops, I cannot find firewall reports
on the server...but they are on the workstations. Move all the workstations
into that new group, then sit back and wait for someone to start yelling
that a firewall pop-up keeps showing. OK, not really, do this after hours.

Look for any popups related to port 25 (when mail clients are closed, in
case any users have POP accounts that send on port 25).

Gregg Hill

Posted with

SBS 2003 Backup Tool don't work with Dell RD1000

OBTS — Wed, 04 Jul 2007 19:14:01 GMT

Date: Wed, 20 Jun 2007 12:14:32 +0100
From: Fernando Morais <fernandodotmoraisatimsitodpt>
Subject: SBS 2003 Backup Tool don't work with Dell RD1000.
Newsgroups: microsoft.public.windows.server.sbs

Hi,

I'm installing a new SBS 2003 Premium that came with a external USB Dell RD1000 storage for backups. But when i try to configure the backup too in SBS it gives and error saying that the RD1000 is not a valid drive.Does anyone had this problem before and if so is there any solution for this?

I've checked older posts but it didn't helped much, tricks with usb pen drives is not a great solution.

Thank you.
Fernando

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

From: <KeithLawrenceMCP discussions microsoft com>
Subject: RE: SBS 2003 Backup Tool don't work with Dell RD1000.
Date: Wed, 20 Jun 2007 08:46:01 -0700
Newsgroups: microsoft.public.windows.server.sbs

Fernando,

I had a similar problem with an Iomega Rev drive. The issue seemed to be (in that case) that SBS didnt pick up its drive letter as a valid location to save data. I think it was driver related.

There is a workaround however!

Run the backup configuration on the SBS but point the save location to a local folder on your server (c:\backup) for example. Once complete, open regedit and navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SmallBusinessServer\Backup

Change the Backup Location Path key to reflect the drive letter of your drive unit. Close regedit and open Server Management. Click backup and you should now see the correct path listed.

Its not ideal and you will need to do it every time you change the backup details but it works.

I hope it also works for your Dell drive!

Keith

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

Date: Sat, 23 Jun 2007 23:57:36 +0100
From: Fernando Morais
Subject: Re: SBS 2003 Backup Tool don't work with Dell RD1000.
Newsgroups: microsoft.public.windows.server.sbs

Hi,

Perfect!

That did the trick and it's a clean way to do it. I don't expect to redo the backup settings very often. It worked perfeclty.

Thanks for the tip.

Fernando

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

From: "Kevin Weilbacher [SBS-MVP]" <kweilbacMVPatgtedotnet>
Subject: Re: SBS 2003 Backup Tool don't work with Dell RD1000.
Date: Sat, 23 Jun 2007 22:45:51 -0400
Newsgroups: microsoft.public.windows.server.sbs

Fernando, here's the link to Sean Daniel's blog where he posted this fix last year. Sean has lot's of other valuable tips as well!

http://blogs.technet.com/sbs/archive/2006/08/29/452501.aspx

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"

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

Date: Mon, 25 Jun 2007 10:34:51 +0100
From: Fernando Morais
Subject: Re: SBS 2003 Backup Tool don't work with Dell RD1000.
Newsgroups: microsoft.public.windows.server.sbs

Thank you Kevin.

An extra source of tips is always welcome.

Posted using

Adding an additional internal webpage

OBTS — Wed, 04 Jul 2007 19:03:33 GMT

From: "asdf" <sdfatasddotcom>
Subject: Adding an additional internal webpage
Date: Mon, 11 Jun 2007 10:59:12 -0500
Newsgroups: microsoft.public.windows.server.sbs

How can I make a folder on my server to be accessable in the same way //companyweb is?

Say the floder is " D:\Website\test" and everyone on the network can just go to //testweb to access it

Thanks
asdf.

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

From: "Costas" <cpstechgroupatgmaildotcom>
Subject: Re: Adding an additional internal webpage
Date: Mon, 11 Jun 2007 12:50:20 -0400
Newsgroups: microsoft.public.windows.server.sbs

Goto IIS Manager, under 'Web Sites' right click and select 'New web site'. Finish the wizard. Goto 'DNS' and create an A record that that points to the IP address of the server using the name you want to use to access the site.

This process will create a website. NOT a SharePoint website. If you want to create a SharePoint website you have to user 'SharePoint Central Administration' to extend the site you created above

Costas

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

Date: Mon, 11 Jun 2007 11:49:16 PST
Subject: Re: Adding an additional internal webpage
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

In addition to what Costas suggests, it should be noted that for SBS2003 and WSS 2, the new site should not be given a new IP. You should use all unassigned and a host header of testweb. The DNS entry should be an alias record and reference back to the server box.

Creating a new virtual server, rather than a subsite of the default server is probably a good idea, but you still want to use the SharePoint application pool.

If you really, really want to use a separate IP for the new Virtual Server, be sure to bind the IP to the LAN NIC before you try to create the Virtual Server in the IIS manager wizard. Be aware that SBS does not like multiple IPs bound to its LAN NIC, and the EICWizard will begin doing strange stuff the next time you have to use it. It took a while for LanWench and Susan Bradley to get me to do this, but it cleared up a bunch of strange things that were happening to my system.

--
Hollis Paul
Mukilteo, WA USA

Posted using

SBS 2003 Setup.exe vs. Vista

OBTS — Wed, 04 Jul 2007 18:04:24 GMT

Newsgroups: microsoft.public.windows.server.sbs
Subject: SBS 2003 Setup.exe vs. Vista
From: "Rob B." <notonatusedotnet>
Date: Sun, 10 Jun 2007 22:41:40 GMT

I added the first Vista client to an SBS 2003, SP1 domain. Until now, all clients were WinXP, SP2. Office 2007 is installed on the XP clients, and the Vista client, which may not be pertinent to this problem.

As is normal, "\\SERVER\Clients\Setup\setup.exe /s SERVER" is executed when a user logs on to any domain client. On the Vista client, I always get the dialog -- regardless of the account privilege -- asking for permission to run Setup.exe. It is annoying. Occasionally, the Program Compatiblity Assistant will appear and advise there's a known compatiblity issue with Setup.exe. It points to KB article 926505 for resolution. The title of the KB is, "Windows Small Business Server 2003: Windows Vista and Outlook 2007 compatibility update."

When I run the SBS2003SP1-KB926505-X86-ENU.EXE fix, I get the error: "This update cannot be installed. Either it is already installed as part of an existing service pack, or it requires a more recent service pack. For more information, see the systems requirements on the download page."

Intially, Windows Server 2003 SP2 was installed, but I uninstalled it because of that error message. Reverting back to SP1 did not correct the situation.

I'm officially stuck. Ideas?

Rob B.

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

From: "Kevin Weilbacher [SBS-MVP]" <kweilbacMVPatgtedotnet>
Subject: Re: SBS 2003 Setup.exe vs. Vista
Date: Sun, 10 Jun 2007 20:32:48 -0400
Newsgroups: microsoft.public.windows.server.sbs

you need to install the Ripcurl patch on your SBS 2003 server that's designed to support both Vista workstations and Outlook 2007:

http://msmvps.com/blogs/bradley/archive/2007/06/08/vista-quot-ripcurl-quot-patch-on-microsoft-update.aspx

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"

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

From: "bass_player [SBS-MVP]" <bass_playeratmvpsdotorg>
Subject: Re: SBS 2003 Setup.exe vs. Vista
Date: Mon, 11 Jun 2007 09:32:25 +0800
Newsgroups: microsoft.public.windows.server.sbs

And download this documnt as well to guide you through the process

Using Windows Vista and Outlook 2007 in a Windows Small Business Server 2003
Network
http://www.microsoft.com/downloads/details.aspx?FamilyID=46E95C56-1A4C-45BD-8D69-5F41FF8F1F22&displaylang=en

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

Newsgroups: microsoft.public.windows.server.sbs
Subject: Re: SBS 2003 Setup.exe vs. Vista
From: "Rob B."
Date: Tue, 12 Jun 2007 04:45:30 GMT

I went through the suggested documentation prior to making my original post here, but read the docs again just to make sure. I also tried again to apply the ripcurl fix, but still have the same error mentioned in my original post

So, for the time being, I have REM'd out the only line in the SBS_LOGIN_SCRIPT.bat file (\\server\Clients\Setup\setup.exe /s server).

I am uncertain of the impact beyond not getting certain applications (IE6, OL2003) and service packs automatically installed on new clients. Are there any other impacts?

Rob B.

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

From: v-terliuatonlinedotmicrosofttodcom (Terence Liu [MSFT])
Date: Wed, 13 Jun 2007 10:20:59 GMT
Subject: Re: SBS 2003 Setup.exe vs. Vista
Newsgroups: microsoft.public.windows.server.sbs

Hello Rob,

Thank you for posting here.

According to your description, I understand that you can not install fix KB926505 on your SBS 2003 and get error message. If I have misunderstood the problem, please don't hesitate to let me know.

Based on my research, KB891193 installation did not complete may relate to that Small Business Server 2003 has been partially updated and may not work properly. I suggest we try the following steps to see if we can resolve this issue:

Please go through the following document to download the 5 parts of SBS 2003 sp1 and install them on the SBS 2003 in turn. Downloading and Installing Windows Small Business Server 2003 Service Pack 1

http://download.microsoft.com/download/e/0/f/e0fee8ce-768d-41c0-8871-9bc48e0b3fc3/ToDownLoadFilesandReadInstructions.htm

Note: The 5 parts:
Windows Server 2003 Service Pack 1

Windows SharePoint Services 2.0 Service Pack 1

Exchange Server 2003 Service Pack 1

Windows XP SP2 for Client Deployment

Windows Small Business Server 2003 Service Pack 1

Then, try to install the KB891193 again.

If we can not resolve the issue after we perform the above steps, please kindly help me collect some information for further investigation:

1. Please capture screenshots on the error messages and send the pictures to me at v-terliuatmicrosoftdotcom

2. Use the MPS report to capture the server configurations for further analysis:
a. Download MPSrepot_network from
http://download.microsoft.com/download/b/b/1/bb139fcb-4aac-4fe5-a579-30b0bd915706/MPSRPT_NETWORK.EXE

b. Run MPSRPT_NETWORK.exe on the server box.

c. The tool will automatically collect the information. This procedure will take 10~15 minutes.

d. Open Windows Explorer, navigate to the folder: %SystemRoot%\MPSReports\Network\Reports\Cab\

e. Send the .cab file directly to me at v-terliuatmicrosoftdotcom

Hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

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

Newsgroups: microsoft.public.windows.server.sbs
Subject: Re: SBS 2003 Setup.exe vs. Vista
From: "Rob B."
Date: Mon, 25 Jun 2007 04:21:03 GMT

Terence,

For the benefit of all, here are the results:

After selecting the option to display Updates in the Add/Remove Programs list, I saw that KB891193 was already installed. However, KB926505 still would not install as per the previous discussion here.

I opted for a clean, off-line installation, including a reformat of the boot/system drive. Immediately after, I installed the 5 parts of SP1. On the final (5th) step, Windows Small Business Server 2003 Service Pack 1, the process failed and displayed the following error message:

"Windows Small Business Server Service Pack 1 Setup has encountered an error. For more information, review the most recent entry in the Setup error log in C:\Program Files\Microsoft Integration\Windows Small Business Server 2003\logs\setup.log. Then correct the error and run Service Pack 1 Setup again."

The referenced setup.log contained no hint of any errors, instead showing that everything was successful. I tried re-installing the SP a couple more times with the same result.

I decided to press on and connected to the Internet, letting Windows Update figure out what else was needed. By the time it was through, KB926505 had been installed and, after re-configuring the Vista client for the new domain, have not had a problem with the default SBS_LOGIN_SCRIPT.bat file when logging on with a limited user account.

As additional information, prior to the rebuild, the server was running WSUS 3.0, WSS 2, SAV Server, and a 3rd party FTP server (GeneFTP). For now, it's strictly SBS 2003, SP2. I'll try WSS 3 next, but that's for another day. Thank you for your help.

Best,
Rob B.

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

From: Terence Liu [MSFT]
Date: Mon, 25 Jun 2007 10:34:38 GMT
Subject: Re: SBS 2003 Setup.exe vs. Vista
Newsgroups: microsoft.public.windows.server.sbs

Hello Rob,

Thank you for kind update.

I'm glad to hear that you can install KB926505 on your SBS, and your Vista client can work fine now.

For the SBS 2003 sp1 installation error, since you do not find any error in the setup log, I think we can ignore this error.

If you still have concern on the SBS 2003 sp1 installation error, please try to create a new thread to get further investigation.

I'd like to make a summary for this post:

Issue:
=============
Can not install hotfix KB926505 on SBS 2003, and get error:

"This update cannot be installed. Either it is already installed as part of an existing service pack, or it requires a more recent service pack. For more information, see the systems requirements on the download page."

Resolutions:
=============
Reinstall SBS 2003 sp1:
Downloading and Installing Windows Small Business Server 2003 Service Pack 1
http://download.microsoft.com/download/e/0/f/e0fee8ce-768d-41c0-8871-9bc48e0b3fc3/ToDownLoadFilesandReadInstructions.htm

Please do not hesitate to post in this great newsgroup if you need any assistance in the future. I look forward to working with you again.

Thank you and have a nice day,

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

Posted using

Sharepoint Portal limitations?

OBTS — Wed, 04 Jul 2007 17:43:23 GMT

From: "Bikini Browser" <removedotbikinitodbrowserdottthisattgmailttodcom>
Subject: Sharepoint Portal limitations?
Date: Sat, 9 Jun 2007 12:05:21 -0400
Newsgroups: microsoft.public.windows.server.sbs

Hello everyone...

Question..

Is the Sharepoint Portal included with SBS 2003 R2 the same as the standalone product or is the SBS version limited in any way?

Thanks in advance...

Bikini Browser

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

Date: Sat, 09 Jun 2007 09:24:46 PST
Subject: Re: Sharepoint Portal limitations?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Actually, you have never received Sharepoint Portal as part of Windows Server. It has always been just WSS, first 2.0, and with R2, 3.0. (SBS MVPs--Correct me if I am wrong on the version numbers--I haven't been interested in R2. I'm waiting for D2. Or perhaps Go Dot.) You get the full Windows Sharepoint Services product, just not the Portal product, which should be on a separate member server.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Bikini Browser"
Subject: Re: Sharepoint Portal limitations?
Date: Sat, 9 Jun 2007 12:40:59 -0400
Newsgroups: microsoft.public.windows.server.sbs

Thanks for your promt reply...

I don't know anything about SharePoint, so bare with me if I sound totally
silly...

You said... >>You get the full Windows Sharepoint Services product, just
not the Portal product,<,

I will be using SBS 2003 R2. Does this mean I will get more than just the Portal? Are you saying that I will get EVERYTHING I NEED in SBS 2003 R2 to setup a SharePoint customer? I don't need any more software, is that correct?

Additionally, If I am going to use SharePoint, do you think I should get the Premium Edition which includes SQL server? Do I need the SQL server for SharePoint?

Please be 100% clear for a Novice like me...

Thanks so much for your answers...

Bikini Browser

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

Date: Sat, 09 Jun 2007 11:38:11 PST
Subject: Re: Sharepoint Portal limitations?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

In article , Bikini Browser wrote:
> I will be using SBS 2003 R2. Does this mean I will get more than just the
> Portal? Are you saying that I will get EVERYTHING I NEED in SBS 2003 R2 to
> setup a SharePoint customer? I don't need any more software, is that
> correct?
>
SharePoint is a product that allows non-IT personnel to set up web sites. I have no idea what you might need to set up any customer.

> Additionally, If I am going to use SharePoint, do you think I should get the
> Premium Edition which includes SQL server? Do I need the SQL server for
> SharePoint?
>
I believe that the WSS that comes with SBS is installed with some version of MSDE, or some such acronym. It is not SQL server. It also does not support searches. If you have SQL server in your system somewhere, then you can use that rather than MSDE; but you have to convert your MSDE database to an instance of an SQL database.

> Please be 100% clear for a Novice like me...
>
Well, perhaps you should leave the beach where you would not be so distracted. There is a Microsoft SharePoint website that presents the material at a level that even a manager can understand:
http://www.microsoft.com/SharePoint/default.mspx

It has been a long time since I was a novice in SharePoint, so I am not very good at generating the kind of support you need. If no one else joins this thread, make a new post. But please, visit that web site first.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Claus" <cjobesatnova-techdotorg>
Subject: Re: Sharepoint Portal limitations?
Date: Sat, 9 Jun 2007 15:38:34 -0400
Newsgroups: microsoft.public.windows.server.sbs

There are 2 different products available: SharePoint Services and the Portal Server. SBS comes with SharePoint Services.

I must agree with Hollis. Go to the SharePoint website and read up on the differences and features for the 2 products.

--
Claus

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

From: "Costas" <cpstechgroupatgmaildotcom>
Subject: Re: Sharepoint Portal limitations?
Date: Sat, 9 Jun 2007 19:17:38 -0400
Newsgroups: microsoft.public.windows.server.sbs

SharePoint Services 3.0 (WSS 3.0) is a technology that runs on Windows Server 2003 (SBS 2003 included) and it is distributed for free. SharePoint Services 2.0 comes with SBS 2003 and if you want to install version 3.0 you have to download it from Microsoft's web site and do a parallel install (there is a document that describes how to do that on the web site).

SharePoint, as a technology component, needs SQL Server to function. If you don't have SQL Server on your server, the installation routine installs MSDE (for version 2.0) or SQL Server Express (for version 3.0) which is limited to 4GB of data. If you develop a SharePoint site and your planning indicates higher amount of data over a period of time, then you'll need to buy the SBS 2003 R2 Premium to take advantage of SQL Server Workgroup which has no data limit.

SharePoint Server 2007 2007 is a server product that operates on top of SharePoint Services. Prior to this release, the name of the server was SharePoint Portal Server 2003. The word "Portal" is not used anymore. This product is not free, and it has specific CAL requirements, all of which you can find at the Microsoft web site.

You don't need SharePoint Server 2007 to develop an application using this technology. WSS will do just fine.

Hope that helps

Costas

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

From: "Bikini Browser"
Subject: Re: Sharepoint Portal limitations?
Date: Tue, 3 Jul 2007 11:53:41 -0400
Newsgroups: microsoft.public.windows.server.sbs

Your detailed information has been very helpful. Thank you!

Bikini Browser

Posted using

How does a SBS network connect to my shiny, new HD DVD player?

OBTS — Sat, 26 May 2007 23:21:57 GMT

Date: Sun, 29 Apr 2007 20:07:07 PST
Subject: How does a SBS network connect to my shiny, new HD DVD player?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

My HD DVD player has an Ethernet connection with which they expect to download firmware update. How would I go about setting this up on my SBS2003 network, with ISA 2004 running?

I guess that it would be similar to how NAS volumes are accessed; with the exception that NAS volumes usually do not call home and expect to chat with a server.

The device will also use a NTP server to acquire time, but that should only mean talking to the SBS2003 server box, no?

--
Hollis Paul
Mukilteo, WA USA

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

From: "Russ Grover $SBITS.Biz$" <support atREMOVETHISDOTSBITSTODBiz>
Subject: Re: How does a SBS network connect to my shiny, new HD DVD player?
Date: Sun, 29 Apr 2007 21:04:06 -0700
Newsgroups: microsoft.public.windows.server.sbs

Well Downloading stuff Usually doesn't matter it's only if the unit would Upload or share itself to the net.

Most NAS units can update firmware by you downloading them saving them to some drive and then updating it.

The Time sync of this unit you won't probably use the SBS since you don't
login to it.
But one of the ones below
time.nist.gov
clock.isc.org
timekeeper.isi.edu
usno.pa-x.dec.com
tock.usno.navy.mil
tick.usno.navy.mil"

And there are many others, however I don't know if it will pass on the time sync through ISA?
(Someone else may help because I've never had to sync something with an external Time source through ISA)

You may have to open port 123 through but I'd try to see if it synced first.

And what kind if DVD Player has a Ethernet port? Is this a Game system thing or a business related item?

If this is the XBox thing, just bring it home to download the Firmware.

Russ

--
Russell Grover
SBITS.Biz
Microsoft Certified Small Business Specialist.
MCP, MCPS, MCNPS, (MCP-SBS)
support @ SBITS.Biz
Remote SBS2003 Support
http://www.SBITS.Biz

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

Date: Mon, 30 Apr 2007 07:57:40 PST
Subject: Re: How does a SBS network connect to my shiny, new HD DVD player?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks, Russ. I never really paid attention to when I could download stuff. But I do recall that the Win2k3 wants to check for upgrades even before the other stuff is installed.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Brian Cryer" <brianc@127.0.0.1.activesol.co.uk>
Subject: Re: How does a SBS network connect to my shiny, new HD DVD player?
Date: Mon, 30 Apr 2007 12:42:24 +0100
Newsgroups: microsoft.public.windows.server.sbs

Never had a dvd player that would connect to a network, interesting. If its only for a firmware update I'd be inclined to never plug it in unless I found I needed a firmware update.

I would have thought it would pull down its IP address and more importantly gateway and ntp server information (if any) from your DHCP server. In which case it should just be a case of plugging it into your network and letting it get on with whatever it does.

Whether ISA will cause a problem ... I've no idea. Sorry.
--
Brian Cryer
www.cryer.co.uk/brian

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

Date: Mon, 30 Apr 2007 07:57:40 PST
Subject: Re: How does a SBS network connect to my shiny, new HD DVD player?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks, Brian. I did neglect to say that I don't run DHCP, but use fixed IPs. But, wouldn't the device have to log into the domain to get that info from the DHCP? I can specify it manually, so I will stick with the fixed IP, but if the list of internet savy devices grows larger, I may rethink the matter. I wonder if a DVD player would require a CAL to do this. I shouldn't think so, as it normally would live off-line, with the TV, unless I carry it up to the computer room. I suspect that the scenario they envision is an internet connection through cable. But then, why would one need a DVD player of the cable connection can download video content.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Jeff Teel" <jdteel atRMoveThis sugardogdotcom>
Subject: Re: How does a SBS network connect to my shiny, new HD DVD player?
Date: Mon, 30 Apr 2007 08:07:27 -0400
Newsgroups: microsoft.public.windows.server.sbs

This may or may not help you but I had a similar situation when plugging in a D-Link Media player into an SBS (Premium) network. The player was assigned an IP address by DHCP but it also needed access to the Internet to be able to download firmware updates ect. In order to allow that to happen I had to make a new rule in ISA that gave Internet access to the media player. This rule dealt with just the media player so it would now give Internet access to just anyone that plugged into the network.

The rule looks like this when viewing it in ISA 2004 list of policy's:

Name: D-Link Media Internet Access
Action: Allow
Protocol: All Outbound Traffic
From/Listener: D-Link Media
To: External
Condition: All Users

The rule is placed towards the bottom of the rule list just above the SBS Internet Access Rule. I can't remember if I had to put it there to make it work or that is just where it ended up but I (think) I had to place it there!

Jeff

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

Date: Mon, 30 Apr 2007 07:57:40 PST
Subject: Re: How does a SBS network connect to my shiny, new HD DVD player?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

This does sound like what I will have to deal with. There are parameters to specify where to get proxy services and dns services. Thanks, Jeff.

--
Hollis Paul
Mukilteo, WA USA

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

Date: Sun, 20 May 2007 07:54:48 PST
Subject: Re: How does a SBS network connect to my shiny, new HD DVD player?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Turns out I didn't have to do anything with SBS. I just had to tell the HD_DVD player where the sbs, dns, and proxy servers were. It was a piece of cake, though slow, to download the 37 parts of the upgrade. Alas, it did not solve the interface problems with the HDMI cable. It seems that the player used a later version of the HDMI spec than did the TV. Bummer. But the component video cable (RGB) worked and prodvided a HD signal.

--
Hollis Paul
Mukilteo, WA USA

Posted using

Should I have the Web Client Service running on the SBS2003 server?

OBTS — Sat, 26 May 2007 23:07:03 GMT

Date: Tue, 17 Apr 2007 20:47:01 PST
Subject: Should I have the Web Client Service running on the SBS2003 server?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

I have just figured out how to create Network Places to my IIS websites on the server from my Vista client computer. This requires that the Web Client Service be running, WebDAV Extensions allowed on the site, and Integrated authentication allowed on the site.

The Web Client Service had been disabled up until now. Is it dangerous to have it running on the SBS2003?

--
Hollis Paul
Mukilteo, WA USA

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

From: v-robeli atonlinedotmicrosofttodcom (Robert Li [MSFT])
Date: Thu, 19 Apr 2007 06:49:40 GMT
Subject: RE: Should I have the Web Client Service running on the SBS2003 server?
Newsgroups: microsoft.public.windows.server.sbs

Hi Hollis,

Thanks for posting in our newsgroup.

Here is the answer to your question:

Q: Is it dangerous to have Web Client service running on the SBS2003?

A: A security issue has been identified in the Web Client service that could allow an attacker to compromise your Windows-based system and gain control over it. So please visit Microsoft update site to download and install latest Service Packs and updates before you enable Web Client service on SBS 2003 Server.

For more information, please refer to:

Security Update for Windows Server 2003 64-bit Itanium Edition and Windows XP 64-bit Itanium Edition, Version 2003 (KB896426)
http://www.microsoft.com/downloads/details.aspx?FamilyId=2024382A-14A9-4231-8835-E2720C562190&displaylang=en

Vulnerability in Web Client Service Could Allow Remote Code Execution (911927)
http://www.microsoft.com/technet/security/bulletin/ms06-008.mspx

MS05-028: A vulnerability in the Web Client Service could allow remote code execution
http://support.microsoft.com/kb/896426/

Hope the information helps.

If you need further assistance, please don't hesitate to let me know.

Best regards,

Robert Li(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

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

Date: Sun, 29 Apr 2007 20:26:50 PST
Subject: Re: Should I have the Web Client Service running on the SBS2003 server?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

> Security Update for Windows Server 2003 64-bit Itanium Edition
>
Thank you, Robert. I had figured that this thread was dead. I just sort of assume that if the SBS MVPs don't jump all over me and tell me I am pig headed that it must be OK. I am not likely to ever go to a 64-bit version of SBS, but I will check out these KB articles. And yes, I did enable the web client service.

--
Hollis Paul
Mukilteo, WA USA

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

From: (Robert Li [MSFT])
Date: Mon, 30 Apr 2007 08:16:32 GMT
Subject: RE: Should I have the Web Client Service running on the SBS2003 server?
Newsgroups: microsoft.public.windows.server.sbs

Hi Hollis,

Thanks for updating.

If you are running Web Client service running on the SBS2003, please pay attention to install the latest Service Packs and hotfixes from Microsoft update website.

For more information, please refer to:

Windows Defender Home
http://www.microsoft.com/athome/security/spyware/software/default.mspx

823166 Overview of Exchange Server 2003 and Antivirus Software
http://support.microsoft.com/?id=823166

If you need further assistance, please don't hesitate to let me know.

Best regards,

Robert Li(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

Posted using

Time hasn't bumped with daylight savings time.

OBTS — Sat, 26 May 2007 22:57:41 GMT

Date: Sun, 11 Mar 2007 11:03:23 PST
Subject: Time hasn't bumped with daylight savings time.
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

My time, which is set to come from one of the time servers, has not changed with the new daylight savings time. I was looking in the System Events list, and the last event for W32Time was an event on 1/9/2007 saying that the client was receiving either no data or bad data from time-nw.nist.gov. No events since. Does that mean that it has been getting good time data since then? And, if yes, are they sending GMT or PDT?

--
Hollis Paul
Mukilteo, WA USA

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

From: "Russ Grover $SBITS.Biz$" <support atREMOVETHISDOTSBITSTODBiz>
Subject: Re: Time hasn't bumped with daylight savings time.
Date: Sun, 11 Mar 2007 12:23:14 -0700
Newsgroups: microsoft.public.windows.server.sbs

Hollis,
It should have changed.
(Reguardless if it grabing the atomic time clock time, Because that just grabs the Min/Sec your PC sets the Time Zone it's in.) Do you have all the Updates on the Servers/PCs

Also make sure that your server is not set to "Arizona" Time zone, and set to "Pacific Time (US and Canada)"

If this still hasn't changed I'd go to.

http://support.microsoft.com/gp/cp_dst

And see if there is something there to help.

But I just checked all my clients servers, and they changed just fine (Thank God)

Russ
--

Russell Grover
SBITS.Biz
Microsoft Certified Small Business Specialist.
MCP, MCPS, MCNPS, (MCP-SBS)
support @ SBITS.Biz
Remote Computer Support
http://www.SBITS.Biz

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

Date: Sun, 11 Mar 2007 13:26:37 PST
Subject: Re: Time hasn't bumped with daylight savings time.
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks, Russ, for the suggestion.

They have all kinds of stuff for me. And even one for Exchange. But I bet that the Exchange one is about meetings and appointments, and I don't use that feature. I've never seen the sense of making an appointment to meet myself.

Does anyone know if the Exchange update does any more than that?

--
Hollis Paul
Mukilteo, WA USA

**********

It really is a bummer that one can't save the page to disk using IE7. I would ordinarily save such a page to a Word file, but one doesn't have Word on the server. Fortunately, WordPad is there to save in rtf format. But this dynamic xhtml isn't helping the user at all.

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

From: "Frank McCallister SBS MVP"
Subject: Re: Time hasn't bumped with daylight savings time.
Date: Sun, 11 Mar 2007 15:30:59 -0500
Newsgroups: microsoft.public.windows.server.sbs

Hi Hollis

To be more precise to Russ the Atomic clocks transmit full time information in GMT and your computer converts it to local time. Your servers and Clients should be upgraded to the new DST patches by Microsoft Update NOT just Windows Update to get ALL the patches unless you are running WSUS. There is also a last minute Sharepoint patch at

http://blogs.technet.com/sbs/archive/2007/03/09/new-sharepoint-2-0-dst-update-and-data-update-tool.aspx

which will not be on MU or WSUS for awhile.

--
Frank McCallister SBS MVP
MCP Microsoft Small Business Specialist
COMPUMAC

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

From: "Russ Grover $SBITS.Biz$"
Subject: Re: Time hasn't bumped with daylight savings time.
Date: Sun, 11 Mar 2007 13:36:24 -0700
Newsgroups: microsoft.public.windows.server.sbs

I never really thought about it but, I guess you are right it does transmit the GMT time and your PC changes it.

Makes more sense.

Thanks

Russell Grover
SBITS.Biz
Microsoft Certified Small Business Specialist.
MCP, MCPS, MCNPS, (MCP-SBS)
support @ SBITS.Biz
Remote Computer Support
http://www.SBITS.Biz

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

Date: Sun, 11 Mar 2007 15:36:36 PST
Subject: Re: Time hasn't bumped with daylight savings time.
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks, Frank, for the precision. That answers the real question about why the time didn't change.

Tell me again about how much I love an old cat that hops down from the bed box in well of the desk and barfs on the rug sample where I put my feet. Grrr!

There are worse things than time not updating with the daylight bump. If I wait three weeks, then the problem disappears, no?

--
Hollis Paul
Mukilteo, WA USA

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

From: "Steve"
Subject: Re: Time hasn't bumped with daylight savings time.
Date: Sun, 11 Mar 2007 17:17:48 -0700
Newsgroups: microsoft.public.windows.server.sbs

If you don't apply the server and workstation patches you'll deal with this again manually in the fall and every spring and fall thereafter.

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

Date: Sun, 11 Mar 2007 19:27:54 PST
Subject: Re: Time hasn't bumped with daylight savings time.
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Now, that is overly pessimistic. After all, the express install works on the principle that each update is independent of all the rest. So, the DLT fix should be independent of the prior one's also. Particularly, since it is probably just a replacement of tables that define day-light savings time. Probably a large table, but still, just a table, not code.

> If All Patches, and Service packs, have been installed, And it still Didn't
> Change
>
I haven't done them for a couple of weeks. I want any that fail to get updated and replaced before I pull them down. I will do the one first, and if that doesn't fly, then get the rest.

> If you don't apply the server and workstation patches you'll deal with this
> again manually in the fall and every spring and fall thereafter.
>
Not necessarily so. Congress did this to save energy. Yet the response to their hasty action may have cost more than the savings in energy. When the analysis is finished, they will surely change their stance and rescind all this fuforah. You can tell I am an optimist.

But, that point did come to mind as I was posting the message.

--
Hollis Paul
Mukilteo, WA USA

Posted using

SBS 2003 sharepoint - read-only docs when trying to edit

OBTS — Fri, 02 Feb 2007 16:44:10 GMT

From: Oscar <Oscar discussions microsoft com>
Subject: SBS 2003 sharepoint - read-only docs when trying to edit
Date: Wed, 24 Jan 2007 07:23:44 -0800
Newsgroups: microsoft.public.sharepoint.general

Hello All, I have the same issue using Sharepoint 2003 and Office Xp. I have tried a lot of solutions and still doesn't work. Did you fix the problem? Can you help me?

Best Regards

Oscar

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

From: rmzl <rmzl discussions microsoft com>
Subject: Re: SBS 2003 sharepoint - read-only docs when trying to edit
Date: Sun, 28 Jan 2007 02:46:01 -0800
Newsgroups: microsoft.public.sharepoint.general

Same problem here. Opening (the right way) is only read only, even for files I have uploaded myself. Explorer view says it all: \\server\..... access denied.:-(

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

From: Stevo DaDevo <StevoDaDevo discussions microsoft com>
Subject: Re: SBS 2003 sharepoint - read-only docs when trying to edit
Date: Wed, 31 Jan 2007 15:30:00 -0800
Newsgroups: microsoft.public.sharepoint.general

Having the same problem with Sharepoint 3.0 and Office 2003. Anybody find a solution yet?

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

From: rmzl
Subject: Re: SBS 2003 sharepoint - read-only docs when trying to edit
Date: Wed, 31 Jan 2007 23:24:00 -0800
Newsgroups: microsoft.public.sharepoint.general

Problem fixed on my system:

A download manager (IE Plugin) was responsible for the read-only behavior (still don't beleive it!!). Uninstalling didn't fix!! Had to revert to a ackup image. 2. Ofiice 2003 SP2 fixed the explorer view problem.

Posted using

Suggestions for removing dead PC names from AD

OBTS — Tue, 02 Jan 2007 03:34:23 GMT

From: "John"
Subject: Suggestions for removing dead PC names from AD
Date: Sun, 31 Dec 2006 13:01:41 -0800
Newsgroups: microsoft.public.windows.server.sbs

Does anyone have any tips on keeping the PC names current on AD. As time goes on people PC's get replaced etc and the names aren't reused. I am starting to see this "creep" appearing at some of my clients sites. Does anyone have a method to say scan a network to see what machines have been used in the last say 60 days or so? Just trying to keep things clean at their sites.

Thanks

John

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

From: "Les Connor [SBS MVP]" <les.connor at DEL dot cfive tod ca>
Subject: Re: Suggestions for removing dead PC names from AD
Date: Sun, 31 Dec 2006 16:08:57 -0600
Newsgroups: microsoft.public.windows.server.sbs

SBS Updates Services (WSUS) might help here. It reports warnings for client computer that haven't contacted the WSUS server for 7 days or more. You could use that bit of reporting to investigate why.

--
Les Connor [SBS MVP]

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

From: "Merv Porter [SBS-MVP]" <mwport at no_spam_hotmail dot com>
Subject: Re: Suggestions for removing dead PC names from AD
Date: Sun, 31 Dec 2006 18:26:58 -0500
Newsgroups: microsoft.public.windows.server.sbs

I wonder if DSQuery would help here...

Pruning Old Computer Accounts in AD
http://www.windowsnetworking.com/kbase/WindowsTips/Windows2003/AdminTips/Admin/PruningOldComputerAccountsinAD.html

Windows Server 2003 Service Pack 1 Administration Tools Pack
http://www.microsoft.com/downloads/details.aspx?FamilyID=E487F885-F0C7-436A-A392-25793A25BAD7&displaylang=en

Or maybe,

OldCmp
http://www.joeware.net/win/free/tools/oldcmp.htm

Merv Porter [SBS-MVP]
============================

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

From: "John"
Subject: Re: Suggestions for removing dead PC names from AD
Date: Mon, 1 Jan 2007 10:42:26 -0800
Newsgroups: microsoft.public.windows.server.sbs

I have used WSUS and my Trend Console too. I was just wondering if there was a tool out there that was specific to this issue.

John

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

From: "Cary Shultz" <cwshultz at mvps dot org>
Subject: Re: Suggestions for removing dead PC names from AD
Date: Mon, 1 Jan 2007 19:40:26 -0500
Newsgroups: microsoft.public.windows.server.sbs

Everyone would benefit immensely from going over to http://www.joeware.net and looking at all of his free tools. The tool specific to this question would be oldcmp. All of his tools are awesome. He is one of the top brains when it comes to Active Directory. Eventually - or so he has stated - he will make tools for sale. I am waiting for that day to come! Who knows. Maybe it already has...

--
Cary W. Shultz
Roanoke, VA 24012

Posted using

Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4

OBTS — Thu, 14 Dec 2006 18:26:56 GMT

Subject: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul
Date: Sun, 26 Nov 2006 16:17:52 PST
Newsgroups: microsoft.public.windows.server.sbs

"Microsoft Internet Security and Acceleration Server 2000 with Service
Pack 2 (SP2) Release Notes"

"ISA Server 2004 Service Pack 2 Internet Security and Acceleration Server 2004"

Are these two documents different views of the same thing? I was under the impression that ISA 2000 SP2 replaced ISA 2000 with ISA 2004. Is ISA Server 2004 SP2 really ISA server 2000 SP4? Can someone fill me in with the begats. I understand the initial begat: SBS2003 Premium Technologies begat ISA Server 2000 for use in SBS2003. How does it go from there?

--
Hollis Paul
Mukilteo, WA USA

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

Date: Sun, 26 Nov 2006 17:53:32 -0800
From: "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa att pacbell dot net>
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent
of SP4
Newsgroups: microsoft.public.windows.server.sbs

No they are two separate products Hollis.

ISA 2004 sp2 is not ISA 2000.

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

From: "Steve"
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Date: Sun, 26 Nov 2006 19:39:44 -0800
Newsgroups: microsoft.public.windows.server.sbs

As Susan says they're not the same. SBS 2003 PE originally included ISA 2000. When SP1 for SBS 2003 was released it included an upgrade to ISA 2004 for those with PE. ISA 2004 is now at SP2.

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

From: v-terliu att online tod microsoft dot com (Terence Liu [MSFT])
Date: Mon, 27 Nov 2006 03:57:48 GMT
Subject: RE: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Newsgroups: microsoft.public.windows.server.sbs

Hello Hollis,

Thank you for posting here. Thank you for Susan and Steve's reply.

According to your description, I understand that you have some misunderstanding about ISA edition history.

ISA server 2000 sp2 and ISA server 2004 sp2 are not the same thing. After ISA server 2000 sp2, Microsoft published ISA server 2004. ISA server 2004 has 2 editions, standard edition and enterprise edition.

And ISA server is integrated with SBS 2003 premium edition. SBS 2003 premium includes ISA server 2000 standard sp2; SBS 2003 premium sp1 includes ISA server 2004 standard sp1. However, SBS 2003 standard edition does not include ISA server.

After ISA server 2004 sp2, Microsoft published ISA server 2006. ISA server 2006 also has 2 editions, standard edition and enterprise edition.

Here is the edition list about ISA server:

========
ISA 2004
========

ISA 2004 MMC, click on Help -> About Microsoft ISA Server 2004

ISA 2004 Standard without service pack Version 4.0.2161.50

ISA 2004 Standard with Service pack 1 Version: 4.0.2163.213

ISA 2004 Standard with Service Pack 2 Version: 4.0.2165.594

Program Files\Microsoft ISA Server\WSPSRV.EXE version reflects ISA server
version.

========
ISA 2000
========

ISA 2000 Standard without Service Pack
Program Files\Microsoft ISA ServerWSPSRV.EXE version 3.0.1200.50

ISA 2000 Standard with Service Pack 1
WSPSRV.EXE version 3.0.1200.166

ISA 2000 Standard SP1 with feature pack 1
WSPSRV.EXE version 3.0.1200.235

ISA 2000 Standard SP2 with feature pack
WSPSRV.EXE version 3.0.1200.365

(Install Secure ID or URL Scan update will not change the version number.)

Hope above info helps.

Thank you and have a nice day.

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

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

Date: Mon, 27 Nov 2006 12:41:36 PST
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks Susan, Steve, and Terrence,

As I have SBS2003 Premium with SP1, I should now be installing ISA server SP2, which will enable Outlook, on my WinXP_x64 client, to connect to Exchange?

--
Hollis Paul
Mukilteo, WA USA

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

From: Terence Liu [MSFT]
Date: Tue, 28 Nov 2006 01:27:20 GMT
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Newsgroups: microsoft.public.windows.server.sbs

Hello Paul,

Thank you for kind update.

Based on my research, after you install ISA 2004 server, I suggest you to perform the following steps to enable internal Outlook to access Exchange server on SBS:

1. After you install ISA, I suggest you rerun CEICW Wizard to make ISA rule to allow Outlook access Exchange server. The following KB will give you detail about how to run this wizard:

825763 How to configure Internet access in Windows Small Business Server 2003
http://support.microsoft.com/?id=825763

Note: The wizard will create a access rule named SBS Protected Networks Access Rule, and this rule will allow Outlook access Exchange server.

2. Please install ISA firewall client on internal Outlook machine:

a. On client machine, run \\SBSServerName\mspclnt

b. Double-click setup.exe to install the firewall client

After above 2 steps, you can try to access Exchange server from internal Outlook client.

Hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

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

Date: Mon, 27 Nov 2006 19:39:02 PST
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul <nospam@nospam.com>
Newsgroups: microsoft.public.windows.server.sbs

In article , Terence Liu [MSFT]
wrote:
> After above 2 steps, you can try to access Exchange server from internal
> Outlook client.
>
Terence,

There has been some history on this subject, which you might want to look
at. The following is a brief synopsis:
******************************
From: "Charlie Russel - MVP" <Charlie@mvKILLALLSPAMMERSps.com>
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64
client?
Date: Sat, 9 Sep 2006 21:56:28 -0700
Newsgroups: microsoft.public.windows.server.sbs

Are you trying to reach outlook from inside or outside ISA?

If you're inside, see:
http://msmvps.com/blogs/xperts64/archive/2005/11/03/74274.aspx There's a fix you may need.

--
Charlie.
http://msmvps.com/blogs/xperts64

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

From: "Charlie Russel - MVP" <Charlie@mvKILLALLSPAMMERSps.com>
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64
client?
Date: Sun, 10 Sep 2006 10:41:49 -0700
Newsgroups: microsoft.public.windows.server.sbs

Then you're probably running in to an ISA issue, and there's a hot fix for it. This hot fix _is_ included in ISA 2k4 SP2, by the way, according to my sources.

--
Charlie.
http://msmvps.com/blogs/xperts64

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

Date: Sat, 09 Sep 2006 18:33:38 PST
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64
client?
From: "Hollis Paul [MVP - Outlook]" <nospam@nospam.com>
Newsgroups: microsoft.public.windows.server.sbs

In article <1157849965.713261.205210@p79g2000cwp.googlegroups.com>,
Shashank wrote:
> Yes, inside that share you have a MSI file, you need to execute that
> and make it work. Firewall client should not be installed on the Server
> in any case, just the clients ;-).
>
It gives an error that says the firewall client cannot be installed on a WinXP-64 client. You would think it would install on the x64 directories.

Is this what you mean by "make it work"?

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

From: "Charlie Russel - MVP" <Charlie@mvKILLALLSPAMMERSps.com>
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64
client?
Date: Sat, 9 Sep 2006 21:54:04 -0700
Newsgroups: microsoft.public.windows.server.sbs

You need the newly released client for XP x64. More info on my blog...
http://msmvps.com/blogs/xperts64/archive/2006/09/05/ISA-Firewall-Client-for-x64.aspx

And direct to download:
http://www.microsoft.com/downloads/details.aspx?familyid=45855498-66ba-43d3-a8f1-37837d380389&displaylang=en

--
Charlie.
http://msmvps.com/blogs/xperts64
********************************

So, there is more to the problem than just running the CEICWizard. In fact, CEICWizard has produce a whole host of rules relating to XML files, WSS sites, and, rule Number 44:

SBS Protected Access Rule
Allow
All Outbound Traffic
From: All Protected Networks
To: All Protected Networks
Conditions: All Users

Even with this, the WinXP x64 Outlook client reports that it cannot connect to the Exchange Server on the SBS2003 Server, which is at SP1.

Charlie says I need to install ISA 2004 SP2. I have already downloaded ISA2004SE-KB903676-x86-ENU.msp. The original question, though badly worded, was which of those two articles I should be reading for this product install. Probably neither. But the KB article doesn't really talk about my situation, either, as the X64 client is on my local network and not a branch office. However, I recognize that a SP fixes more than one problem, and the hot-fix I need is included there.

I do wonder if that other stuff about the branch off will really bollix the whole ISA operation and halt all communication with the SBS2003 from all my clients? Surely, Microsoft wouldn't release something that would do that! But then there was the Hell upgrade to Outlook that killed most Outlook developer applications. That was sort of like preventing all communications with the server, and Microsoft released that without so much as a sorry about that, you all, but our reputations depend on it. But I digress.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Andrew H" <ajhpms at hotmail dot com>
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Date: Tue, 28 Nov 2006 16:38:19 +0200
Newsgroups: microsoft.public.windows.server.sbs

There's an update to the ISA client that allows installation on x64 machines:

http://www.microsoft.com/downloads/details.aspx?FamilyID=45855498-66BA-43D3-A8F1-37837D380389&displaylang=en

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

From: Terence Liu [MSFT]
Date: Wed, 29 Nov 2006 10:03:58 GMT
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Newsgroups: microsoft.public.windows.server.sbs

Hello Paul,

Thank you for kind update.

I completely understand what you worry about. However, please do not fear for ISA SP2 installation.

Of course, you can backup your SBS server by NTbackup before you install ISA SP2, or you can export complete configuration of your ISA. The following pages will give some detail:

Backing Up and Restoring Windows Small Business Server 2003
http://go.microsoft.com/fwlink/?LinkId=49916

Export, Import, and Backup Functionality in ISA Server 2004
http://www.microsoft.com/technet/isa/2004/plan/exportimportsettings.mspx

Then please download ISA sp2 form the following link:
http://www.microsoft.com/downloads/details.aspx?familyid=88350ABA-D09E-44B5-8002-96590ABFA148&displaylang=en

Note: there is a word document about this sp2 in this page: ISA Server 2004 Service Pack 2.doc, you can read it first.

After you download it, please double-click ISA2004SE-KB903676-x86-ENU.msp and install SP2.

Additional, please move rule 44 SBS Protected Access Rule to top and click Apply button to save the configuration.

If the issue persists, please kindly help me collect some information for further investigation:

1. Please help to gather the ISA Info:

1) Download the file from the following URL:

http://www.isatools.org/tools/isainfo.zip

2) Extract all files to a folder on ISA server.

3) Double click Isainfo.js. This will generate 2 files: ISAInfo2004-<computer-name>.log and ISAInfo2004-<computer-name>.xml in the current folder.

4) Please send these files to me at v-terliu@microsoft.com

2. Please follow the link and download and run the Microsoft Internet Security and Acceleration (ISA) Server 2004 Best Practices Analyzer Tool and then send me the results.

http://www.microsoft.com/downloads/details.aspx?FamilyId=D22EC2B9-4CD3-4BB6-91EC-0829E5F84063&displaylang=en

3. Please also help to gather the ISA logs:

1) Schedule a down time.

2) Open ISA 2004 management console.

3) Expand the server node and highlight 'Monitoring'.

4) In the right pane, switch to the 'Logging' tab, make sure the 'Task Pane' is showed there.

5) In the 'Task Pane', click 'Configure Firewall Logging' under 'Logging Tasks', and then switch the 'log storage format' from 'MSDE database' (default) to 'File'.

6) Switch to the 'Fields' tab, click 'Select All', and then click OK.

7) In the 'Task Pane', click 'Configure Web Proxy Logging' under 'Logging Tasks', and then switch the 'log storage format' from 'MSDE database' (default) to 'File'.

8) Switch to the 'Fields' tab, click 'Select All', and then click OK.

9) Click 'Apply' to save changes and update the configuration.

10) Temporarily disable the Firewall service. To do that, please click Monitoring | Services tab, and then right click 'Microsoft Firewall' to choose 'Stop'.

11) Clear the current existing W3C logs. To do that, go to the log saving directory and clean any existing .W3C logs. By default, the logs will be saved to 'C:\Program Files\Microsoft ISA Server\ISALogs'. (Some MDF may not be able to deleted, that's normal.) You may backup them first and then delete them.

12) Go back to the ISA 2004 management console, and then Start the stopped 'Microsoft Firewall' service.

13) Reproduce the problem, stop the service, and then gather the resulting W3C files to me for analysis.

14) Please also let me know the IP address of the testing clients so that I can filter the data.

Hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

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

Date: Fri, 01 Dec 2006 08:10:38 PST
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

In article <, Terence Liu [MSFT] wrote:
> I completely understand what you worry about. However, please do not fear
> for ISA SP2 installation.
>
Thanks, Terence. Impressive post! I will begin checking things out this coming week.

--
Hollis Paul
Mukilteo, WA USA

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

From: Terence Liu [MSFT]
Date: Mon, 04 Dec 2006 08:50:07 GMT
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Newsgroups: microsoft.public.windows.server.sbs

Hello Paul,

Thank you for reply.

I am currently standing by for an update from you and would like to know how things are going on your end. If you have any questions or concerns on the recent information I've provided you, please don't hesitate to let me know.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

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

Date: Tue, 05 Dec 2006 19:33:07 PST
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Actually, all the hardware pieces finally arrived, so I took the server in to the shop today to have a new motherboard inserted into its underbelly, and new memory, and a new video AGP built in and support for USB 2.0. It will be have one huge bellyache till I can get a big dollop of repair reinstall down its gullet so that it can appreciate its new hardware. Then I'll work on the ISA2004 sp2. (The temp server is dual booting with the X64 client workstation so it really isn't relevant for now.) NNTP was bollixed all day today until I imported all the protocol rules from the other server. Now I can at least post the status report.

--
Hollis Paul
Mukilteo, WA USA

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

From: Terence Liu [MSFT]
Date: Thu, 07 Dec 2006 11:38:58 GMT
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Newsgroups: microsoft.public.windows.server.sbs

Hello Paul,

Thank you very much for your update.

I was just writing to say that I hope everything is going well.

Please do not hesitate to let me know if this problem reoccurs or if there's anything else I can do for you.

Thank you and have a nice day,

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

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

Date: Fri, 08 Dec 2006 15:33:15 PST
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

The server box is back from the shop, with a new 64-bit motherboard. Oddly enough, the box boots up to SBS2003. The network adapters were bollixed, so I started in to reset the fixed IP and stuff. When I OK'd the TCP/IP properties of the LAN connector, it ground away for a while, then gave me a blue screen of death and wrote all 2Gig of memory to disk. But, when I booted up again, the TCP/IP properties of that network adapter were still there and it was working fine. I then fixed the parameters of the WAN adapter and it took without any problems. I went to the internet and activated the changes. I could Google. I didn't try Exchange.

Does anyone think I should still do a repair/reinstall just to be safe?

--
Hollis Paul
Mukilteo, WA USA

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

Date: Fri, 08 Dec 2006 20:28:38 PST
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Exchange works, even after forklifting the databases back from the backup server.

I have also installed ISA2004 SP2. Now the x64 WinXP client opens Outlook and I can see the email boxes as I did before.

ISA2004 now keeps asking me if I want to open a site on my trusted list. Is there any way to suppress that query and automatically return a yes? Are there any other settings I should make to ISA2004 SP2?

--
Hollis Paul
Mukilteo, WA USA

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

From: Terence Liu [MSFT]
Date: Mon, 11 Dec 2006 04:53:30 GMT
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Newsgroups: microsoft.public.windows.server.sbs

Hello Paul,

Thank you for kind update.

Based on my research, this issue may refer to Internet Explorer Enhanced Security Configuration component.

For more information about Enhanced Security Configuration, click the following article number to view the article in the Microsoft Knowledge Base:

815141 Internet Explorer Enhanced Security Configuration changes the browsing experience
http://support.microsoft.com/?id=815141

Disable the Internet Explorer Enhanced Security Configuration component. To do this, follow these steps:

1. Click Start, point to Control Panel, and then click Add or Remove Programs.

2. Click Add/Remove Windows Components.

3. In the Windows Components Wizard dialog box, click to clear the Internet Explorer Enhanced Security Configuration check box in the Components box.

4. Click Next, and then click Finish.

If the issue persists, please kindly help me collect some information for further investigation:

1. Please capture a screenshot on the window which keep asking you and send
the picture to me at v-terliu@microsoft.com

2. If you can success access the web sites after click Yes?

3. Is this issue only happens on server side? Do clients have same problem?

...

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

Date: Fri, 08 Dec 2006 20:28:38 PST
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

In article, Terence Liu [MSFT] wrote:
> 815141 Internet Explorer Enhanced Security Configuration changes the
> browsing experience
> http://support.microsoft.com/?id=815141
>
OK, I grabbed up this article and carefully adjusted the security levels in the trusted sites and Intranet sites. I also moved Intranet sites from trusted to Intranet sites. So far, I haven't encountered the problem again, but I haven't used that client much since then.

--
Hollis Paul
Mukilteo, WA USA

Posted using

Remote Access Problem

OBTS — Tue, 12 Dec 2006 06:25:14 GMT

From: =?Utf-8?B?S2VtY28=?= <Kemco@discussions.microsoft.com>
Subject: Remote Access Problem
Date: Fri, 11 Aug 2006 13:31:02 -0700
Newsgroups: microsoft.public.windows.server.sbs

I have a customer who is experiencing an ongoing problem with their Remote Access.

They Have MS SBS 2003 Standard Edition and have a Zyxel Zywall 5 Internet firewall appliance. The deal is that it is all set up and working properly and in approximately every day or so it will say server cannot be found. Once they go in and run the remote access wizard again the problem stops and they are able to access with no problem. They are using the Zywall to configure the DHCP and have a manual IP set for the Server. I am not sure what is going on and if someone could help it would be very much appreciated.

Thank you all for your help.

Joe

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

From: "Cris Hanna $SBS-MVP$"
Subject: Re: Remote Access Problem
Date: Fri, 11 Aug 2006 16:03:12 -0500
Newsgroups: microsoft.public.windows.server.sbs

I would strongly encourage you to turn off DCHP and any DNS on the Zyxel unit and have SBS provide these services as designed.

--
Cris Hanna [SBS-MVP]

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

From: "Russ SBITS.Biz $MCP SBS$" <support att sbits ttod biz>
Subject: Re: Remote Access Problem
Date: Fri, 11 Aug 2006 15:08:00 -0700
Newsgroups: microsoft.public.windows.server.sbs

This Advice assumes you are running 1 NIC in your SBS box.

Having DHCP by the sbs box is Preferred and you will make your life easier.
I'm not trying to dis Cris, (Because what he said is Best Practice and Advice)

But you can keep the router as DHCP (I have some clients I go around and around on this.) But there is a fix.

First your SBS box must be correctly setup for the DNS to your ISP's (PRI & SEC)

Then set the Primary DNS of the Router to the SBS box and the Secondary As your ISP's

Then put in the Login Script
ipconfig /flushdns

Really not needed all the time, but instead of going to all the pcs.. After you do this, all your PC's should have no problem seeing things.

If of course you still have problem, you will have to disable the DHCP on the Router.. Enable it on your SBS box, and Set scope etc etc...

Russ

--
Russell Grover
SBITS.Biz
Enterprise Solutions for Small Business
Microsoft Certified Small Business Specialist.
MCP, MCPS MCNPS, (MCP-SBS)
Portland/Beaverton Oregon USA
Live Support
href="http://www.sbits.biz/livehelp"http://www.sbits.biz/livehelp
Support @ SBITS.Biz
href="http://www.SBITS.Biz"http://www.SBITS.Biz

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

From: "Steve Friedl [MVP]" <steve at uniwiz dot net>
Subject: Re: Remote Access Problem
Date: Sat, 12 Aug 2006 08:22:42 -0700
Newsgroups: microsoft.public.windows.server.sbs

Russ SBITS.Biz (MCP SBS)" wrote:

"Then on the Router.
Then set the Primary DNS of the Router to the SBS box and the Secondary As your ISP's"

I believe this is a very bad idea: when plugging in the IP address of multiple DNS servers, they must all return the same data for any given query or hard-to-debug problems will arise.

Of course, asking the SBS box and your ISP's nameserver for (say) href="http://www.unixwiz.net"www.unixwiz.net will both return the same data, and this applies to the whole internet at large, but for the *internal* domain of the SBS box - perhaps unixwiz.local - the two nameservers have no chance of returning the same data. the ISP won't ever have an answer for this even though the SBS box would be fully able to answer it, so it will return "No such domain" to those who ask.

This is a recipe for havoc.

XP (at least) uses negative DNS caching, where "No such domain" is taken as an affirmative response rather than a transient failure, so they *remember that response*. This means that if the SBS machine is unavailable for even a moment, clients on the network asking for (say) server.unixwiz.local will learn that the name has no value, and won't try the other machine later: they "know" that it's a bad lookup.

Considering how much Windows relies on DNS for Active Directory stuff, negative caching of the local will destroy an entire network in short order, and the only real fix is to wait it out (for the TTL to expire) or reboot everything. It's awful, and completely avoidable.

If the SBS machine is the only machine providing DNS, it's actually better if clients get a timeout/no response error during DNS lookups, because these are considered transitory and will be retried in short order - there is no negative caching in this case.

It's true that when SBS is down you also won't be able to surf the internet (which wouldn't be affected one way or another by this negative caching thing), the downside is so ugly that we-can't-be-down environments should just get a second box to run AD-integrated DNS. Then either one of them can provide authoritative answers for the local domain or the public internet.

I suppose it's possible to try hard and configure your router to do DHCP, but it's unlikely that it's going to be able to provide all the same information that the SBS box will, and getting dynamic DNS to work is going to be a lot more tricky. This is just a poor idea, but not the same kind of really bad idea that splitting your DNS authorities is.

Steve

--
Steve Friedl / UNIX Wizard / Microsoft Security MVP / href="http://www.unixwiz.net"www.unixwiz.net

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

Date: Sat, 12 Aug 2006 13:20:04 PST
Subject: Re: Remote Access Problem
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

You avoid this by putting the ISP's name servers in the DNS forwarders list, and they are queried only after DNS have found no local reference.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Russ SBITS.Biz $MCP SBS$"
Subject: Re: Remote Access Problem
Date: Sat, 12 Aug 2006 20:59:27 -0700
Newsgroups: microsoft.public.windows.server.sbs

UH, I'd hate to argue but it works perfect. Never had any DNS issues...

The SBS Takes care of DNS, and if it's down, then the Router will use the ISPs DNS

Works Perfect, or it has for years anyway?

And Hellis is correct if you do have that issue, just make a DNS entry...

Russ

--
Russell Grover
SBITS.Biz
Enterprise Solutions for Small Business
Microsoft Certified Small Business Specialist.
MCP, MCPS MCNPS, (MCP-SBS)
Portland/Beaverton Oregon USA
Live Support
http://www.sbits.biz/livehelp
Support @ SBITS.Biz
http://www.SBITS.Biz

Posted using

Forklifting Exchange databases between SBS2003 systems

OBTS — Tue, 12 Dec 2006 04:34:29 GMT

Date: Sat, 09 Sep 2006 14:44:06 PST
Subject: Forklifting Exchange databases between SBS2003 systems
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

As everyone knows by now, I have spent this summer migrating my SBS2003 system to new hardware, and applying SBS2003 SP1 to both them. This has been accomplished. I am trying to keep the Exchange databases in sync by forklift from the source system to the migrated system. I followed Jeff Middleton's instructions for forklifting from SBS2000 to SBS2003; which you can review at http://msmvps.com/blogs/obts/archive/2005/02/09/35514.aspx

Everything works except the public folder database will not mount. But Outlook will open and the email is all there. Does anybody know what needs to be tweaked to get the Public Folder database to mount in a SBS2003 to SBS2003 forklift?

--
Hollis Paul
Mukilteo, WA USA

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

From: "Shashank" <phoenixwithashes at gmail tod com>
Newsgroups: microsoft.public.windows.server.sbs
Subject: Re: Forklifting Exchange databases between SBS2003 systems
Date: 9 Sep 2006 17:45:38 -0700

What is the erro message you get? Anyway try this:

Goto Program files/exchsrvr/bin folder through the command prompt and run eseutil /mh "the database path for pub1.edb" and see if it says "Dirty shutdown" for the state in output. If it does, you need run eseutil /p switch this time and repir the public database. After that, stop MSExchangeIS and delete the log and chk files or move them and then start MSExchangeIS and mount the public store.

Regards,
Shashank

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

Date: Sun, 10 Sep 2006 12:04:11 PST
Subject: Re: Forklifting Exchange databases between SBS2003 systems
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

I was looking for something related to my DSL service, and decided that I must have squirreled it away in the public folder. But when I went to look at it, the public folders would not open. It was mounted, but I couldn't see any folders when I drilled down in the Server Management display. So, I ran your command against it, and it says it was a clean shutdown.

And this is on the SBS2003, SP1, server that is the source of the forklift in the original message. Any suggestion on what to do with the public folders on this server?

--
Hollis Paul
Mukilteo, WA USA

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

Date: Tue, 12 Sep 2006 16:59:14 -0700
From: "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
Subject: Re: Forklifting Exchange databases between SBS2003 systems
Newsgroups: microsoft.public.windows.server.sbs

What is the exact error that you are getting?

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

Date: Wed, 13 Sep 2006 10:23:34 PST
Subject: Re: Forklifting Exchange databases between SBS2003 systems
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Source: MSExchangeIS
Type: Error Event ID: 9519

Error Oxfffff9bb starting database "First Storage Group\Public Folder Store(OBTS01)" on the Microsoft Exchange Information Store.

In the byte field, it says, Failed to configure MDB.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Jeff Middleton [SBS-MVP]" <jeff at cfisolutions dot com>
Subject: Re: Forklifting Exchange databases between SBS2003 systems
Date: Wed, 13 Sep 2006 11:42:26 -0500
Newsgroups: microsoft.public.windows.server.sbs

Hollis,

I'll take a moment first to clarify that for anyone who is working from the book chapter I wrote on Swing Migration, the content of that chapter was cut for total book page length and that forced the removal of all of the troubleshooting section (for the entire project path), including the Exchange "it didn't work, what do I do" parts. The Technician Kit includes that 16 pg section. After SBS SP1 was released, I wrote an additional Release Notes reference that since the last time it was updates is now another 15 pgs, and it does address issues specific to Exchange.

Coincidental with the time of the release of SBS SP1, I also added a 65 pg summary reference to the Technician Kit called the Exchange Forklift Guide which was explicitly to address the entire range of issues that seemed to be confusing people doing Swing and getting stuck or confused at the point of moving Exchange, troubleshooting existing Exchange problems prior to moving it, and resolving cleanup issues.

So my main point here isn't "if you don't have a kit, buy the kit", rather to clarify that supporting this particular issue isn't necessarily a simple process, it's something that I have committed about 100 pgs of authoritative reference information to document and clarify based upon supporting the population who are using the Kit and coming to me to claim their free direct support from me because they have a Kit.

Moving Exchange via a Forklift is not a horribly complicated process if all things are in good condition, but it's a horribly difficult process to troubleshoot once you get off track. Why? Because MS doesn't support this, they don't even produce a document that identifies that it can be done, and therefore none of the KBs they have out there actually summarize a troubleshooting condition to get you out of the conditions you can observe. Exchange troubleshooting is an implicitely confusing process because the error messages you see quite often are actually misleading about the problem.

I can tell you that the most common mistakes made in Forklift are:

- Failling to remove existing logs, or bringing over the original logs
- Failing to set correct root partition and folder level permissions.
- Failing to match namespace
- Failing to move to the same or higher SP level
- Moving damaged databases
- Failing to follow my documentation on post-forklift cleanup and tuning.

If you are working from a Technician Kit, anyone is welcome to come to me directly for the support they have coming to me. If you are working from the book chapter, I can tell you that the manuscript of that section on Exchange was truncated with only the bare minimum I thought would communicate the academic concepts involve, not a complete set of production steps that needed to included necessary troubleshooting steps....and it's now two releases of SBS old and 2 yrs out of date.

The vast majority of troubleshooting steps I ever see on SBS and Exchange posted in public groups are wrong, misdirected, or overkill. I'm just being honest. The reason MS endorses Exmerge (as well as ADMT) is because troubleshooting of Exchange that is lossless, efficient, accurate, appropriate to your situation, and aware of all the context issues involved is hard to google because there's so much crap out there that is just wrong. What it takes to address a project like Swing is vastly easier to align provided that the project steps leading up to the Forklift were properly handled, and that you don't start running around in circles trying things that don't apply simply because an error message you got matches a Google hit from someone else with a completely different set of circumstance.

I would be happy to try to help you here, but I would need to know more about what the problem is. I am happy to help you directly. I'd be extremely pleased to have you or anyone else doing Swing with a Technician Kit to use the discussion forms on my website where 100% of the discussion is constrained to troubleshooting conditions produced or encountered in Swing....and I review all of the posts to ensure that they are to the highest degree possible as lossless, efficient, accurate, appropriate to your situation, and aware of all the context issues involved as I can provide.

If the priv mounted (and you really can see the old mail in the mailboxes now), but the pub didn't, this implies the namespace matches and probably the SP levels are okay. It suggests that the database paths are correct and the permissions are probably correct, but that's not guaranteed. It implies that the priv passed a consistency and corruption check, but that doesn't imply the pub did. It suggests that you can try to diagnose and correct the Pub as a forklift issue, or you could export it to PST and import it back to a new clean pub....then reassign the folder ownerships and permissions. That's probably what CSS would recommend....as would I, but I tend to go the extra mile with anyone I work with supporting directly to preserve a priv or pub if possible....but you really need to have the complete set of references I have written in order to do this in a sane manner. Most people who have the complete documentation, follow the steps and have healthy conditions complete all steps of a forklift within 30 minutes of moving the databases.

- Jeff

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

Date: Wed, 13 Sep 2006 11:36:56 PST
Subject: Re: Forklifting Exchange databases between SBS2003 systems
From: "Hollis Paul [MVP - Outlook]" <nospam@nospam.com>
Newsgroups: microsoft.public.windows.server.sbs

In article Jeff Middleton [SBS-MVP]
wrote:
> I'll take a moment first to clarify ...
>
Thanks, Jeff, for the clarification. It was those hundred pages I didn't want to read, important as they are. I just moved back to a set that was a week old, and they opened fine. I guess that means I can get almost everything copied to a PST.

I do think I need to poke PSS about this and maybe they will write up a KB. A thing to remember is that this happened to the systems that were not forklifted. I can't open the Public Store on the system that was running fine, both Priv and Pub were mounted and processing message requests OK. Now, after SP1 and 43 subsequent critical updates, the Public Store doesn't mount. If PSS doesn't produce a successful result, I will come get your kit.

--
Hollis Paul
Mukilteo, WA USA

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

Date: Sat, 23 Sep 2006 08:17:56 PST
Subject: Re: Forklifting Exchange databases between SBS2003 systems
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Well, PSS didn't do so well on this one. They tried a number of things, even forklifting it back to the server, that is, removing the logs and stuff and just leaving the two mdb and two stm files in MDBDATA and starting the services and mounting the databases. So, the poked around and found evidence that the databases had lived in another system, elicited my explanation of forklifting back and forth, and decided that the databases were so fragile that we had better back them up, by exporting through Outlook to client .pst files, installing blank databases, and importing back through Outlook. Took forever, but it worked. The only problems are that I can't import my Rules, and it would not let me import the public folders under All Public Folders. And I am getting an extra IPM-Tree folder, too boot. So, I will see if they can fix that when they call back on Monday. Must say I could have done all that on my own, if I had know that it was unsafe to repair the original database files. Too bad there isn't a diagnostic tool that can produce more direct evaluations than eseutil.

--
Hollis Paul
Mukilteo, WA USA

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

Date: Sat, 25 Nov 2006 18:29:22 PST
Subject: Re: Forklifting Exchange databases between SBS2003 systems
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

The good news is that after PSS had me rebuild from new databases and both are at the same SP level, the forklift now works. It should be really fast when I get the new motherboard/CPU bundle in the old system's box.

--
Hollis Paul
Mukilteo, WA USA

Posted using

How do I install the ISA2003 firewall client from the WinXP-64 client?

OBTS — Tue, 12 Dec 2006 04:10:28 GMT

Date: Sat, 09 Sep 2006 17:56:58 PST
Subject: How do I install the ISA2003 firewall client from the WinXP-64 client?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

If I do a network places -> MS Windows Network -> domain -> SBSProduction and expand that. I see an entry for mspclnt which has some installation stuff, but is other wise uninformative. Is this where I install the ISA2004 firewall client?

--
Hollis Paul
Mukilteo, WA USA

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

From: "Shashank" <phoenixwithashes at gmail dot com>
Newsgroups: microsoft.public.windows.server.sbs
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: 9 Sep 2006 17:59:25 -0700

Yes, inside that share you have a MSI file, you need to execute that and make it work. Firewall client should not be installed on the Server in any case, just the clients ;-).

Regards,
Shashank

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

From: "SuperGumby [SBS MVP]" <not your nellie>
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sun, 10 Sep 2006 11:30:13 +1000
Newsgroups: microsoft.public.windows.server.sbs

and why is it called mspclient? A throwback to MS Poxy server, though it is indeed the MS Poxy client.

HOWEVER, there is a specific client for 64 bit computers which has only been released recently, it will not be in the \\sbs\mspclient folder.

Shashank, I'm actually wondering about something related to this and a couple of other threads from the last few days.

A) I commonly install the ISAFC on all client PC's (including servers). The only object it does not get installed to is the ISA server itself (mostly SBS). In a recent thread someone commented that they were having problems with server type services, on a box seperate to ISA, and they were advised to remove the ISAFC from the server. Comment?

B) Being EPS I sortta expect you do high level support of specific products, I'm interested in which, got a 'Hi I'm Shashank' page somewhere?

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

From: "Shashank"
Newsgroups: microsoft.public.windows.server.sbs
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: 9 Sep 2006 22:07:28 -0700

Well a 64 bit client wasn't mentioned anywhere earlier. Anyway What David gave is what will work.

Answer to Question A:> No Idea, they must have something messed up on that machine.

Answer to question B:> I Do not have a page, I Support SBS for MSFT and work as an outside consultant to many companies. So the product i support is SBS 2003/2000.

Why would u wanna know about me anyway? :-)

Regards,
Shashank

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

From: "SuperGumby [SBS MVP]"
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sun, 10 Sep 2006 15:39:05 +1000
Newsgroups: microsoft.public.windows.server.sbs

umm, have a look at the topic of the conversation, I think there's a 64 in there somewhere :-)

Though what the hey ISA2003 is I have no idea.

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

From: "Shashank"
Newsgroups: microsoft.public.windows.server.sbs
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: 9 Sep 2006 22:54:17 -0700

Hmm looks like i missied that though i did notice ISA 2003 :-) and i was laughing, that must've been where i lost my concentration.

Anyway, tell me something about u...u gotta "Hi I'm SuperGumpy" page anywhere? And where ur from?

Shashank

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

From: "SuperGumby [SBS MVP]"
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sun, 10 Sep 2006 16:14:33 +1000
Newsgroups: microsoft.public.windows.server.sbs

supergumby.dyndns.org

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

Date: Sun, 10 Sep 2006 10:29:51 PST
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Sorry, guys. I noticed the ISA 2003 later, also. However, one can't do a recall with an NNTP message.

I will try to put the important configuration in the body of the message, also.

--
Hollis Paul
Mukilteo, WA USA

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

From: "David Copeland [MSFT]" <davidcop att online microsoft dot com>
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sat, 9 Sep 2006 21:07:58 -0500
Newsgroups: microsoft.public.windows.server.sbs

Are you using the one that was released this week

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=45855498-66BA-43D3-A8F1-37837D380389

Hope that helps,
David Copeland
Microsoft Small Business Server Support

This posting is provided "AS IS" with no warranties, and confers no rights.

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

Date: Sat, 09 Sep 2006 20:02:23 PST
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
From: Hollis Paul

Newsgroups: microsoft.public.windows.server.sbs

Thanks, David, for the link to the new firewall client.

I just installed it, and added the program Outlook to it. Alas, I still can't start Outlook. It gives a message that Outlook must be on-line to be able to run. Do I have to open a specific port to get Outlook to see the Exchange server on the SBS2003 box?

I might add that Outlook comes up fine on the other clients.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Charlie Russel - MVP" <Charlie mvKILLALLSPAMMERSps com>
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sat, 9 Sep 2006 21:56:28 -0700
Newsgroups: microsoft.public.windows.server.sbs

Are you trying to reach outlook from inside or outside ISA?

If you're inside, see:
http://msmvps.com/blogs/xperts64/archive/2005/11/03/74274.aspx There's a fix you may need.

--
Charlie.
http://msmvps.com/blogs/xperts64

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

Date: Sun, 10 Sep 2006 10:29:51 PST
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks, Charlie. I will download that and give it a whirl.

Inside/Outside? It is a client on my LAN.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Charlie Russel - MVP"
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sun, 10 Sep 2006 10:41:49 -0700
Newsgroups: microsoft.public.windows.server.sbs

Then you're probably running in to an ISA issue, and there's a hot fix for it. This hot fix _is_ included in ISA 2k4 SP2, by the way, according to my sources.

--
Charlie.
http://msmvps.com/blogs/xperts64

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

Date: Sun, 10 Sep 2006 13:29:19 PST
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks again, Charlie. I just downloaded ISA 2k4 SP2 from Bink. I wonder why Windows Update never mentioned it. It calls for WSS SP2, which I thought SBS2003 SP1 installed, but I sure do not know where to check that.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Charlie Russel - MVP"
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sun, 10 Sep 2006 17:36:18 -0700
Newsgroups: microsoft.public.windows.server.sbs

Windows Update won't ever offer ISA patches. Microsoft Update should. But you really should always get patches from the MS site. Nothing against bink. but it's just a good practice.

http://www.microsoft.com/downloads/details.aspx?familyid=88350ABA-D09E-44B5-8002-96590ABFA148&displaylang=en

--
Charlie.
http://msmvps.com/blogs/xperts64

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

Date: Sun, 10 Sep 2006 18:32:11 PST
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

You are probably right. However, I have given up searching for things at the Microsoft.com site. That search engine misses even the most obvious thing. Google presents Bink as equally attractive.

As it turns out, Bink just sent me off to the Microsoft page. So, all is well.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Charlie Russel - MVP"
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sun, 10 Sep 2006 19:36:29 -0700
Newsgroups: microsoft.public.windows.server.sbs

Tip: use google with "site:microsoft.com" at the end of the search string.

FWIW, I used the "live search" in Vista x64 to pop up that link as the first hit for "ISA 2004 SP2 site:microsoft.com" - and I'm not even sure that the site: syntax works in live search.

--
Charlie.
http://msmvps.com/blogs/xperts64

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

Date: Mon, 11 Sep 2006 08:05:32 PST
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

I have downloaded Vista beta, but have never been able to install it. First, the migrated SBS2003 monopolized that box for a long while. Now, I am having so much problem with the SBS2003 SP1 systems that I have no desire to fuss with a OS beta. It just seems like my SBS2003 was a car in a train wreck. Though we have cobbled back the pieces, it just isn't going to run free and easy for the next three years, like the last three. Sigh. And owners of small businesses think they can be their own systems guru and still run their business!

--
Hollis Paul
Mukilteo, WA USA

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

Date: Sat, 09 Sep 2006 18:33:38 PST
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

In article Shashank wrote:
> Yes, inside that share you have a MSI file, you need to execute that
> and make it work. Firewall client should not be installed on the Server
> in any case, just the clients ;-).
>
It gives an error that says the firewall client cannot be installed on a WinXP-64 client. You would think it would install on the x64 directories.

Is this what you mean by "make it work"?

--
Hollis Paul
Mukilteo, WA USA

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

From: "Charlie Russel - MVP"
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sat, 9 Sep 2006 21:54:04 -0700
Newsgroups: microsoft.public.windows.server.sbs

You need the newly released client for XP x64. More info on my blog...
http://msmvps.com/blogs/xperts64/archive/2006/09/05/ISA-Firewall-Client-for-x64.aspx

And direct to download:
http://www.microsoft.com/downloads/details.aspx?familyid=45855498-66ba-43d3-a8f1-37837d380389&displaylang=en

--
Charlie.
http://msmvps.com/blogs/xperts64

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

From: "Cris Hanna [SBS-MVP]"
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sun, 10 Sep 2006 00:51:12 -0500
Newsgroups: microsoft.public.windows.server.sbs

Unfortunately it won't run on Vista RC1 (X86)

--
Cris E. Hanna [SBS-MVP]

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

From: "Charlie Russel - MVP"
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sun, 10 Sep 2006 07:32:27 -0700
Newsgroups: microsoft.public.windows.server.sbs

yes, that is unfortunately true. In an SBS Premium network, my preferred workaround is to use a DHCP reservation for the x64 Vista machine so that I'm certain of its IP address, and then create an ISA rule that allows that IP address (or block of IP addresses if you have several) access. It's a kludge, and not optimal. But until we have a vista ISA client, the best I can do.

--
Charlie.
http://msmvps.com/blogs/xperts64

Posted using

ISA 2006 and SBS2003

OBTS — Tue, 12 Dec 2006 03:29:54 GMT

Date: Tue, 24 Oct 2006 10:51:40 PST
Subject: ISA 2006 and SBS2003
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

ISA 2006 just appeared in my MSDN disks. Will it work on a SBS2003 domain? Has anybody done this yet?

--
Hollis Paul
Mukilteo, WA USA

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

From: "Dave Nickason [SBS MVP]" <gwdibble att frontiernet dot net>
Subject: Re: ISA 2006 and SBS2003
Date: Tue, 24 Oct 2006 14:01:15 -0400
Newsgroups: microsoft.public.windows.server.sbs

Not sure whether it'll work or not, but ISA 2006 won't be supported on SBS
2003.

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

From: "Steve"
Subject: Re: ISA 2006 and SBS2003
Date: Tue, 24 Oct 2006 11:29:57 -0700
Newsgroups: microsoft.public.windows.server.sbs

Put it on a separate box not the SBS 2003 itself.

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

Date: Tue, 24 Oct 2006 11:57:18 PST
Subject: Re: ISA 2006 and SBS2003
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks, Steve.

Better yet, put it in a VM and see if SBS 2003 lives or dies.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Charlie Russel - MVP" <charlie at mvKILLALLSPAMMERSps dot org>
Subject: Re: ISA 2006 and SBS2003
Date: Tue, 24 Oct 2006 11:33:22 -0700
Newsgroups: microsoft.public.windows.server.sbs

Not supported, and probably won't work. Certainly, the CEICW doesn't know anything about it and couldn't be expected to configure it.

--
Charlie.
http://msmvps.com/xperts64

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

Date: Tue, 24 Oct 2006 11:57:18 PST
Subject: Re: ISA 2006 and SBS2003
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks, Charlie. That is an important consideration. One could argue that the CEICW's work is done, if one is already running on ISA2004. Reconfiguring might be tough, but that doesn't happen often once basic connectivity is established. A point to ponder.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Cris Hanna[SBS-MVP]"
Subject: Re: ISA 2006 and SBS2003
Date: Tue, 24 Oct 2006 14:54:25 -0500
Newsgroups: microsoft.public.windows.server.sbs

maybe not for you, but we get people re-running it here all the time....changed ISPs, or whatever.

--
CRIS HANNA [SBS-MVP]
----------------------------------------
Please only communicate in the newsgroup. Please do not contact me
directly.

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

From: "Russ - SBITS.Biz $MCP SBS$"
Subject: Re: ISA 2006 and SBS2003
Date: Tue, 24 Oct 2006 13:20:54 -0700
Newsgroups: microsoft.public.windows.server.sbs

Just look at the Posts 50% or greater is running CEICW to fix it. I personally wouldn't introduce anything to compromise using it.

If you do realize you will be in a Unsupported state. And any trouble you have, you will be on your own.

Russ

--
Russell Grover
Microsoft Certified Small Business Specialist.
MCP, MCPS, MCNPS, (MCP-SBS)
Remote Support Available
MSN Messenger
Support @ SBITS.Biz
http://www.SBITS.Biz

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

Date: Tue, 24 Oct 2006 14:51:53 PST
Subject: Re: ISA 2006 and SBS2003
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

In article <OYc8in69GHA.4712@TK2MSFTNGP03.phx.gbl>, Russ - SBITS.Biz
$MCP SBS$ wrote:
> If you do realize you will be in a Unsupported state.
> And any trouble you have, you will be on your own.
>
That sounds pretty familiar. I did take my three support events for
the last year, but the results were spotty. The SBS support events
that were handled in Austin, Texas, were superb. The ones that went to
India, less than stellar.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Steve Foster [SBS MVP]" <steve dot foster att picamar tod co tod uk>
Subject: Re: ISA 2006 and SBS2003
Newsgroups: microsoft.public.windows.server.sbs
Date: Wed, 25 Oct 2006 05:45:17 -0700

Hollis Paul wrote:
>Thanks, Charlie. That is an important consideration. One could argue
>that the CEICW's work is done, if one is already running on ISA2004.
>Reconfiguring might be tough, but that doesn't happen often once basic
>connectivity is established. A point to ponder.

That connectivity would be unlikely to survive the ISA2004 to ISA2006 upgrade process. But if you're comfortable operating ISA2004 directly, you'd be able to configure ISA2006 manually. There aren't major differences between the two.

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

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

Date: Tue, 24 Oct 2006 11:57:18 PST
Subject: Re: ISA 2006 and SBS2003
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

In article <#QEZnZ59GHA.4524@TK2MSFTNGP04.phx.gbl>, Dave Nickason [SBS MVP]
wrote:
> Not sure whether it'll work or not, but ISA 2006 won't be supported on > SBS2003.
>
Thanks, Dave.

It won't be supported till 2009, no? But then, it will surely be SBS2005.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Kevin Weilbacher [SBS-MVP]" <kweilbacMVP att gte tod net>
Subject: Re: ISA 2006 and SBS2003
Date: Tue, 24 Oct 2006 22:46:15 -0400
Newsgroups: microsoft.public.windows.server.sbs

As said by others, ISA 2006 will not be supproted on SBS 2003.
http://msmvps.com/blogs/bradley/archive/2006/08/06/106919.aspx

OTOH, there is a new ISA firewall Client for ISA 2006 that will also work with ISA 2000 and ISA 2004, and is recommended to be installed. This new FW client will work with 64 bit machines.
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=45855498-66BA-43D3-A8F1-37837D380389

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"

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

From: "Kevin Weilbacher [SBS-MVP]"
Subject: Re: ISA 2006 and SBS2003
Date: Tue, 24 Oct 2006 23:19:36 -0400
Newsgroups: microsoft.public.windows.server.sbs

and you will need to uninstall the old fw client from the workstations, then install the new FW client and then reboot.
http://msmvps.com/blogs/kwsupport/archive/2006/10/24/ISA-2006-and-SBS-2003.aspx

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"

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

Date: Tue, 24 Oct 2006 20:48:06 PST
Subject: Re: ISA 2006 and SBS2003
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thank you, Kevin. That is interesting information. The box I would test it on is a 64-bit box. Alas, I don't have two such boxes, though that was in the plans. Being pitched from the MVP program has put a kibosh on all those plans, so I may have to think it through again.

Damn, I should be crawling your blog. I used to, but creating the jump tables is such a tedious task that I have not done it for "mature" blogs with lots of entries. Perhaps if I do a month a day I would work back far enough in a short while. I need a dull project to keep me out of mischief, anyway.

--
Hollis Paul
Mukilteo, WA USA

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

From: <BHeld discussions microsoft com>
Subject: Re: ISA 2006 and SBS2003
Date: Tue, 14 Nov 2006 18:55:02 -0800

I have installed it on SBS 2003 R2 and have all the essentials working again, Email, internet, DHCP & AD. Web services is what is really kicking my butt right now, apparrently ISA is fighting with IIS on some ports. I would agree that this will work much better on its own box.

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

From: "Dave Nickason [SBS MVP]"
Subject: Re: ISA 2006 and SBS2003
Date: Wed, 15 Nov 2006 10:52:49 -0500
Newsgroups: microsoft.public.windows.server.sbs

For any of the built-in stuff, ISA and IIS should be configured with the CEICW. If you're still fighting with this, please start a new thread where you should be able to get ideas from someone who's already won the battle.

Posted using

Net Time from a computer on the net that logs into a workgroup

OBTS — Tue, 12 Dec 2006 02:32:43 GMT

Date: Sat, 25 Nov 2006 13:04:28 PST
Subject: Net Time from a computer on the net that logs into a workgroup
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

I have one workstation that logs into a workgroup identity. It has a network identity of the same name. That user is able to get email from the Exchange server and surf the internet. However, her time does not update. What do I have to do to get the network time into her workgroup workstation?

Note: she isn't about to log into her network profile and lose access to everything in your workgroup profile.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Russ - SBITS.Biz $MCP SBS$"
Subject: Re: Net Time from a computer on the net that logs into a workgroup
Date: Sat, 25 Nov 2006 17:01:05 -0800
Newsgroups: microsoft.public.windows.server.sbs

Since she doesn't log into the domain she doesn't get the benefit of Time Sync with the server.

But there are a number of tools to time sync with the Atomic clock in Colorado.

In a "WorkGroup" computer if you Double click on the Time (in Lower Right, Assuming it's visible)

You select TAB "Internet Time:"

Check the box to have it sync with MS Time Server (You can add your own time servers just Google for more time servers)

If it seems to loose time daily, Replace the Motherboard CMOS Battery (It's usually size of a quarter and
$2.50 or so)

Russ

--
Russell Grover
Microsoft Certified Small Business Specialist.
MCP, MCPS, MCNPS, (MCP-SBS)
Remote Support Available
Support @ SBITS.Biz
http://www.SBITS.Biz

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

Date: Sat, 25 Nov 2006 19:54:35 PST
Subject: Re: Net Time from a computer on the net that logs into a workgroup
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

I should have said in the first message, but the workstation is WinXP SP2. When I double-click the time in the lower right corner, I get the properties panel. It only has two tabs: Date and Time, and Time Zone. Where does the internet time tab come from?

Is there a script that can be installed, and scheduled, to query the time from the server?

--
Hollis Paul
Mukilteo, WA USA

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

From: "Russ - SBITS.Biz $MCP SBS$"
Subject: Re: Net Time from a computer on the net that logs into a workgroup
Date: Sat, 25 Nov 2006 20:27:32 -0800
Newsgroups: microsoft.public.windows.server.sbs

This line will set the PC's time to the server
net time \\SBS2003SERVER /set /yes

--
Russell Grover
SBITS.Biz
Microsoft Certified Small Business Specialist.
MCP, MCPS, MCNPS, (MCP-SBS)
Remote SBS2003 Support
http://www.SBITS.Biz

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

A lot of jovial banter goes here.

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

From: "Russ - SBITS.Biz $MCP SBS$"
Subject: Re: Net Time from a computer on the net that logs into a workgroup
Date: Sun, 26 Nov 2006 19:24:46 -0800
Newsgroups: microsoft.public.windows.server.sbs

Hollis since this is a Home PC
You can also put atomicclock on it.
It's a small Utility that will sync the PC daily..
http://www.download.com/3000-2350-10061823.html

Russ

--
Russell Grover
Microsoft Certified Small Business Specialist.
MCP, MCPS, MCNPS, (MCP-SBS)
Remote Support Available
Support @ SBITS.Biz
http://www.SBITS.Biz

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

Date: Mon, 27 Nov 2006 08:53:13 PST
Subject: Re: Net Time from a computer on the net that logs into a workgroup
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

That is an interesting thought. I will see if the batch file in the start-up folder works. If it doesn't, I'll try this. Thanks for the info.

--
Hollis Paul
Mukilteo, WA USA

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

Date: Tue, 28 Nov 2006 10:28:41 PST
Subject: Re: Net Time from a computer on the net that logs into a workgroup
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

In article <ePIHvMREHHA.3520@TK2MSFTNGP04.phx.gbl>, Russ - SBITS.Biz
$MCP SBS$ wrote:
> This line will set the PC's time to the server
> net time \\SBS2003SERVER /set /yes
>
Thanks, everyone. This seems to be working. I put it in a bat file in the start-up folder.

--
Hollis Paul
Mukilteo, WA USA

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

From: "kj"
Subject: Re: Net Time from a computer on the net that logs into a workgroup
Date: Sun, 26 Nov 2006 01:07:53 -0700
Newsgroups: microsoft.public.windows.server.sbs

See;

http://support.microsoft.com/kb/314054/en-us

--
/kj

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

From: "Anna Clark" <anna.clark att verizon dot net>
Subject: Re: Net Time from a computer on the net that logs into a workgroup
Date: Mon, 27 Nov 2006 07:57:11 -0500

Hi Hollis:

What would be lost by creating and using a new profile? Her desktop and
documents could easily be copied over. What's left?
--
Regards:

Anna Clark

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

Date: Mon, 27 Nov 2006 08:53:13 PST
Subject: Re: Net Time from a computer on the net that logs into a workgroup
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

I don't really know. But the rule is hands off her computer if it makes any changes to what she knows and does. If changing from workstation user to network user allowed you to use the old documents and settings tree, then I would insist on it. And the profile migration wizard assumes that the migration is to a new computer, so it writes whatever to a floppy disk. Believe me, she has much more than a floppy in that document tree. I have seen no utility that makes the switch easy; so it doesn't get done. Hence, no mucking with the profile. She did that once; doesn't need to do it again.

--
Hollis Paul
Mukilteo, WA USA

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

From: "Lanwench [MVP - Exchange]"
Subject: Re: Net Time from a computer on the net that logs into a workgroup
Date: Mon, 27 Nov 2006 13:27:20 -0500
Newsgroups: microsoft.public.windows.server.sbs

I understand where you're coming from. It isn't worth getting a divorce over, I think. Note however that the file & settings transfer wizard, and the Office "save my settings" wizard, don't require a floppy - you can direct the output wherever you like, such as a local folder or a network folder.

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

Date: Mon, 27 Nov 2006 15:37:18 PST
Subject: Re: Net Time from a computer on the net that logs into a workgroup
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks for the info. I had missed that part. I will see if it works adequately next time she gets a new computer or operating system.

--
Hollis Paul
Mukilteo, WA USA

Posted using

SBS 2003 with Trend Micro C/S/M Suite - Vista Clients

OBTS — Mon, 11 Dec 2006 20:58:33 GMT

From: "Stu Howe" <sheodi att no.spam.please.cogeco tod ca>
Subject: OT: SBS 2003 with Trend Micro C/S/M Suite - Vista Clients
Date: Sun, 10 Dec 2006 09:51:16 -0500
Newsgroups: microsoft.public.windows.server.sbs

Hi all,

We have a nicely running SBS 2003 domain using Trend's CSM Suite.

I have added a Vista client to the domain and now need to add anti virus to the client. I looked around the Trend site but can't seem to decide if the client install packages on the SBS server will work with Vista.

Has anyone tried this? Are there any gotchas? Did I miss info on the Trend site?

Thanks!

Stu

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

From: "Lanwench [MVP - Exchange]"
Subject: Re: SBS 2003 with Trend Micro C/S/M Suite - Vista Clients
Date: Sun, 10 Dec 2006 10:04:12 -0500
Newsgroups: microsoft.public.windows.server.sbs

I don't think it's supported with the current version of OfficeScan, especially since Vista isn't officially released yet. Trend has a beta version (7.8)you can download...

http://endpointsecurity.trendmicro.com/pr/tm/en-us/enterprise/eps/vista.aspx?alsck=35

I also presume this is not intended to be a production workstation and you're just doing testing!

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

From: "Stu Howe"
Subject: Re: SBS 2003 with Trend Micro C/S/M Suite - Vista Clients
Date: Sun, 10 Dec 2006 10:15:11 -0500
Newsgroups: microsoft.public.windows.server.sbs

Hi,

Thanks for the info - I had suspected this was the case.

Actually, Vista IS released now to certain MS Business partners and some selected other recipients. I have the RTM version as I am in the latter group mentioned above.

This is a produciton workstation and Vista is behaving perfectly. Anti virus is the only thing need now. Avast 4.7 was working nicely in previous builds, but I was hoping to keep everything integrated....

Will use Avast until Trend issues an update, which I expect will be very soon.

Thanks again,

Stu

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

Date: Sun, 10 Dec 2006 08:39:09 -0800
From: "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]"
Subject: Re: SBS 2003 with Trend Micro C/S/M Suite - Vista Clients
Newsgroups: microsoft.public.windows.server.sbs

Vista may be released.. but there's a ton of "business bar level" stuff for me that isn't ready.

Trend is one of them.

Posted using

Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4

OBTS — Sat, 02 Dec 2006 19:48:36 GMT

Date: Sun, 26 Nov 2006 16:17:52 PST
Subject: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

"Microsoft Internet Security and Acceleration Server 2000 with Service Pack 2 (SP2) Release Notes"

"ISA Server 2004 Service Pack 2 Internet Security and Acceleration Server 2004"

--
Hollis Paul
Mukilteo, WA USA

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

Date: Sun, 26 Nov 2006 17:53:32 -0800
From: "Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP]" <sbradcpa att pacbell dott net>
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Newsgroups: microsoft.public.windows.server.sbs

No they are two separate products Hollis.

ISA 2004 sp2 is not ISA 2000.

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

From: "Steve"
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Date: Sun, 26 Nov 2006 19:39:44 -0800
Newsgroups: microsoft.public.windows.server.sbs

As Susan says they're not the same. SBS 2003 PE originally included ISA 2000. When SP1 for SBS 2003 was released it included an upgrade to ISA 2004 for those with PE. ISA 2004 is now at SP2.

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

From: v-terliu at online dott microsoft dot com (Terence Liu [MSFT])
Date: Mon, 27 Nov 2006 03:57:48 GMT
Subject: RE: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Newsgroups: microsoft.public.windows.server.sbs

Hello Hollis,

Thank you for posting here. Thank you for Susan and Steve's reply.

According to your description, I understand that you have some misunderstanding about ISA edition history.

After ISA server 2004 sp2, Microsoft published ISA server 2006. ISA server 2006 also has 2 editions, standard edition and enterprise edition.

Here is the edition list about ISA server:

========
ISA 2004
========

ISA 2004 MMC, click on Help -> About Microsoft ISA Server 2004

ISA 2004 Standard without service pack Version 4.0.2161.50

ISA 2004 Standard with Service pack 1 Version: 4.0.2163.213

ISA 2004 Standard with Service Pack 2 Version: 4.0.2165.594

Program Files\Microsoft ISA Server\WSPSRV.EXE version reflects ISA server
version.

========
ISA 2000
========

ISA 2000 Standard without Service Pack
Program Files\Microsoft ISA ServerWSPSRV.EXE version 3.0.1200.50

ISA 2000 Standard with Service Pack 1
WSPSRV.EXE version 3.0.1200.166

ISA 2000 Standard SP1 with feature pack 1
WSPSRV.EXE version 3.0.1200.235

ISA 2000 Standard SP2 with feature pack
WSPSRV.EXE version 3.0.1200.365

(Install Secure ID or URL Scan update will not change the version number.)

Hope above info helps.

Thank you and have a nice day.

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

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

Date: Mon, 27 Nov 2006 12:41:36 PST
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

Thanks Susan, Steve, and Terrence,

As I have SBS2003 Premium with SP1, I should now be installing ISA server SP2, which will enable Outlook, on my WinXP_x64 client, to connect to Exchange?

--
Hollis Paul
Mukilteo, WA USA

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

From: (Terence Liu [MSFT])
Date: Tue, 28 Nov 2006 01:27:20 GMT
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Newsgroups: microsoft.public.windows.server.sbs

Hello Paul,

Thank you for kind update.

Based on my research, after you install ISA 2004 server, I suggest you to perform the following steps to enable internal Outlook to access Exchange server on SBS:

1. After you install ISA, I suggest you rerun CEICW Wizard to make ISA rule to allow Outlook access Exchange server. The following KB will give you detail about how to run this wizard:

825763 How to configure Internet access in Windows Small Business Server 2003
http://support.microsoft.com/?id=825763

Note: The wizard will create a access rule named SBS Protected Networks Access Rule, and this rule will allow Outlook access Exchange server.

2. Please install ISA firewall client on internal Outlook machine:

a. On client machine, run \\SBSServerName\mspclnt

b. Double-click setup.exe to install the firewall client

After above 2 steps, you can try to access Exchange server from internal Outlook client.

Hope these steps will give you some help.

Thanks and have a nice day!

Best regards,

Terence Liu(MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

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

Date: Mon, 27 Nov 2006 19:39:02 PST
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
From: Hollis Paul
Newsgroups: microsoft.public.windows.server.sbs

> After above 2 steps, you can try to access Exchange server from internal
> Outlook client.
>
Terence,

There has been some history on this subject, which you might want to look at. The following is a brief synopsis:

******************************
From: "Charlie Russel - MVP" <Charlie@mvKILLALLSPAMMERSps.com>
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sat, 9 Sep 2006 21:56:28 -0700
Newsgroups: microsoft.public.windows.server.sbs

Are you trying to reach outlook from inside or outside ISA?

If you're inside, see:
http://msmvps.com/blogs/xperts64/archive/2005/11/03/74274.aspx There's a fix you may need.

--
Charlie.
http://msmvps.com/blogs/xperts64

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

From: "Charlie Russel - MVP" <Charlie@mvKILLALLSPAMMERSps.com>
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sun, 10 Sep 2006 10:41:49 -0700
Newsgroups: microsoft.public.windows.server.sbs

Then you're probably running in to an ISA issue, and there's a hot fix for it. This hot fix _is_ included in ISA 2k4 SP2, by the way, according to my sources.

--
Charlie.
http://msmvps.com/blogs/xperts64

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

Date: Sat, 09 Sep 2006 18:33:38 PST
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
From: "Hollis Paul [MVP - Outlook]" <nospam@nospam.com>
Newsgroups: microsoft.public.windows.server.sbs

Is this what you mean by "make it work"?

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

From: "Charlie Russel - MVP" <Charlie@mvKILLALLSPAMMERSps.com>
Subject: Re: How do I install the ISA2003 firewall client from the WinXP-64 client?
Date: Sat, 9 Sep 2006 21:54:04 -0700
Newsgroups: microsoft.public.windows.server.sbs

You need the newly released client for XP x64. More info on my blog...
http://msmvps.com/blogs/xperts64/archive/2006/09/05/ISA-Firewall-Client-for-x64.aspx

And direct to download:
http://www.microsoft.com/downloads/details.aspx?familyid=45855498-66ba-43d3-a8f1-37837d380389&displaylang=en

--
Charlie.
http://msmvps.com/blogs/xperts64
********************************

So, there is more to the problem than just running the CEICWizard. In fact, CEICWizard has produce a whole host of rules relating to XML files, WSS sites, and, rule Number 44:

SBS Protected Access Rule
Allow
All Outbound Traffic
From: All Protected Networks
To: All Protected Networks
Conditions: All Users

Even with this, the WinXP x64 Outlook client reports that it cannot connect to the Exchange Server on the SBS2003 Server, which is at SP1.

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

From: "Andrew H" <ajhpms att hotmail dott com>
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Date: Tue, 28 Nov 2006 16:38:19 +0200
Newsgroups: microsoft.public.windows.server.sbs

There's an update to the ISA client that allows installation on x64 machines:

http://www.microsoft.com/downloads/details.aspx?FamilyID=45855498-66BA-43D3-A8F1-37837D380389&displaylang=en

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

From: (Terence Liu [MSFT])
Date: Wed, 29 Nov 2006 10:03:58 GMT
Subject: Re: Is the SBS Enterprise Server ISA 2000 now up to the equivalent of SP4
Newsgroups: microsoft.public.windows.server.sbs

Hello Paul,

Thank you for kind update.

I completely understand what you worry about. However, please do not fear for ISA SP2 installation.

Of course, you can backup your SBS server by NTbackup before you install ISA SP2, or you can export complete configuration of your ISA. The following pages will give some detail:

Backing Up and Restoring Windows Small Business Server 2003
http://go.microsoft.com/fwlink/?LinkId=49916

Export, Import, and Backup Functionality in ISA Server 2004
http://www.microsoft.com/technet/isa/2004/plan/exportimportsettings.mspx

Then please download ISA sp2 form the following link:
http://www.microsoft.com/downloads/details.aspx?familyid=88350ABA-D09E-44B5-8002-96590ABFA148&displaylang=en

Note: there is a word document about this sp2 in this page: ISA Server 2004 Service Pack 2.doc, you can read it first.

After you download it, please double-click ISA2004SE-KB903676-x86-ENU.msp and install SP2.

Additional, please move rule 44 SBS Protected Access Rule to top and click Apply button to save the configuration.

If the issue persists, please kindly help me collect some information for further investigation:

1. Please help to gather the ISA Info:

1) Download the file from the following URL:

http://www.isatools.org/tools/isainfo.zip

2) Extract all files to a folder on ISA server.

3) Double click Isainfo.js. This will generate 2 files ISAInfo2004-<computer-name>.log and ISAInfo2004-<computer-name>.xml in the current folder.

4) Please send these files to me at v-terliu@microsoft.com

2. Please follow the link and download and run the Microsoft Internet Security and Acceleration (ISA) Server 2004 Best Practices Analyzer Tool and then send me the results