Re: Trend CSM 3.0 will not push to XP clients

Can you log on to the remote computer via RDP?

If so, then do that and browse to the ofcscan share on the server and run
autopcc.exe.

Or, browse to the security dashboard at http(s)://<servername> or
<ip>/SMB/Console/html/cgi/cgiChkMasterPwd.exe <:port> and click on the
'click here to install' link. The stuff in brackets is specific to what
selections you made when you installed.

Or, send the user a link to the above URL via email. You can copy and paste
the url from the console when you're

Or, put \\<servername>\ofcscan\autopcc.exe into the logon script for the
domain.

Or, send the above URL to the user via email.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:uMC09MS8FHA.736@xxxxxxxxxxxxxxxxxxxxxxx
> Hello!
>
> I have contacted Trend tech support with this issue, but no solution has
> been found yet.
>
> I recently installed Trend Micro CSM 3.0 on SBS 2003 SP1 with ISA 2004,
> and I am trying to remotely install to XP Pro SP2 clients using the
> Dashboard > Security Settings > Add Computer > Remote Install method. I
> was trying to install to an XP Pro SP2 client with the Microsoft Firewall
> client installed so it would work with the ISA 2004 on SBS. My first
> attempt to use the remote install method popped up a prompt asking for the
> username and password. It does the same thing trying to install to an XP
> Pro SP2 client without the Microsoft Firewall client (ISA 2004) running.
>
> If I enter the domain admin username and password, or any other
> administrator name and password, I get an error that states, "Remote
> installation unsuccessful. The username and/or password may be invalid, or
> the target computer is running Windows XP using simple file sharing.
> Confirm the username and password. If the target computer is running
> Windows XP, disable simple file sharing." I searched Trend's knowledge
> base and found that exact error, although for version 2.0. The "solution"
> was to use the "domain\username" format when trying to add a desktop using
> the Dashboard > Security Settings > Add Computer > Remote Install, yet it
> still will not install. If I use domain\administrator and the password, I
> get an error stating that "hillservices\administrator does not have
> administrator privileges" in spite of the fact that I use the Domain Admin
> account. I have tried it with other domain admin accounts as well, and
> they also fail.
>
> Trend's response was, in part, "To solve the issue please type in the
> username on the user field without the domain. Please don't use the format
> domain\user or computername\user. Just type in the user and password."
> That did not work, and it was the first method I tried anyway. They also
> said to "... disable simple file sharing...make sure the C$ of the client
> is accessible from the server, verify that file and printer sharing is
> installed on the client and turn off any firewalls in between."
> If I use the username only and not domain\username format, I get a
> "Security Server Management Console" error popup that states, "Remote
> installation unsuccessful. The username and/or password may be invalid, or
> the target computer is running Windows XP using simple file sharing.
> Confirm the username and password. If the target computer is running
> Windows XP, disable simple file sharing."
>
> I got this error the first time I tried a remote installation. I searched
> the knowledge base, and found
> http://kb.trendmicro.com/solutions/search/main/search/solutionDetail.asp?solutionID=19831
> which, although it is for version 2.0, has the identical error message.
> That is why I tried the domain\username format, which resulted in the
> error I first reported ("hillservices\administrator does not have
> administrator privileges").
>
> The XP Pro stations' firewalls are off, simple file sharing is unchecked,
> file and printer sharing is installed, I can browse from the server to the
> C$ share on the workstations, and no other firewalls or AV software are
> present. It does the same thing on another workstation running XP Pro SP2,
> also.
>
> Anybody else have this problem with Trend Micro CSM 3.0?
>
> Thank you for your time!
>
> Gregg Hill
>
>


.

Relevant Pages

  • Re: Trend CSM 3.0 will not push to XP clients
    ... "hillservices\administrator does not have administrator privileges" and If I ... The username and/or password may be invalid...." ... >> was trying to install to an XP Pro SP2 client with the Microsoft Firewall ... >> or the target computer is running Windows XP using simple file sharing. ...
    (microsoft.public.windows.server.sbs)
  • Re: Trend CSM 3.0 will not push to XP clients
    ... Hi Greg when you enter the username are you entering it in the form ... > and I am trying to remotely install to XP Pro SP2 clients using the ... > was trying to install to an XP Pro SP2 client with the Microsoft Firewall ... > the target computer is running Windows XP using simple file sharing. ...
    (microsoft.public.windows.server.sbs)
  • Re: Trend CSM 3.0 will not push to XP clients
    ... The username and/or password may be ... >>> and I am trying to remotely install to XP Pro SP2 clients using the ... >>> was trying to install to an XP Pro SP2 client with the Microsoft ... >>> or the target computer is running Windows XP using simple file sharing. ...
    (microsoft.public.windows.server.sbs)
  • Re: installing programs remotly
    ... > What I wanted to install remotly was UltraVNC. ... XP Home can't turn off Simplified file sharing. ... >> If the remote PC is an XP Pro box look at using Remote Desktop... ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: installing programs remotly
    ... >> What I wanted to install remotly was UltraVNC. ... XP Home can't turn off Simplified file sharing. ... >>> If the remote PC is an XP Pro box look at using Remote Desktop... ...
    (microsoft.public.windowsxp.work_remotely)
Loading