Re: 2.0 distribution points to 2003 distribution points

I am still having problems establishing the new 2003 DP. I added the site
server to the domain admin group. The computers I am attempting to make a DP
are Domain Controller, so I added the site server to the domain admin group.
The components look like they are trying to be installed on the new DP but
it fails.
In the sitecomp.log i recieve and an error

ERROR: NAL failed to access NAL path "MSWNET:\\DC-BROOKS02\admin$\",
probably because the machine is down, the network is down, or the Site System
Connection Accounts are misconfigured. NAL INetworkObject::IsAccessible()
returned 0x80070005: The operation completed successfully.

and then it fails.
The computer is on and active and pingable
It still seems like a permisson problem but I dont know where to add
permissions.
I am using advanced security and only have one site server.
There is a step before that one that looks like its using the same admin$
share but it went thru successful, so it didnt seem like it was that
particular share permisson problem. I havent added the neew servers the
right to write to the system management container in AD, could that be
related?
Any ideas would be appreciated.



"Kim Oppalfens" wrote:

>
> You seem to be on the right track, once you added the site server's
> computer account you should be fine (assuming advanced security).
>
> PS: Kim her post would be his post. Last time I checked I still had all
> the features you would expect from a guy, but I am definitely lacking
> some to be a woman. I am used to be referred as her though, so no
> worries.
> In article <F6256771-8279-49DB-A1E6-EF2E469FF0EC@xxxxxxxxxxxxx>,
> RichardWood@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > I wasn't attempting to run the DP as a 2.0 and 2003 site system, I just
> > wanted to migrate the same server from being a 2.0 DP to a 2003 DP and how
> > that is accomplished. I have successfully removed the 2.0 site systems roles
> > by doing what Kim had reccomended in her post. So I am closer, I go into the
> > 2.0 interface and all of the DP site systems are gone now. I went into the
> > 2003 interrface and under hierarchy>Senders and added the servers i want to
> > be DP's. They now appear under the Hierarchy>Site systems and I went into
> > the porperties of both and enabled them as DP's. But I am still having some
> > errors in the site components
> > under the Site compoenent manager. I look at the errors and it says access
> > denied. It seems like a permission issue. The DP are Domain controllers so
> > I am assuming I have to add the SMS primary site computer name to the Domain
> > Admin group and everything should work. I just wanted to post the staus of
> > my problem in case someone else has a similar issue.
> > "Stan White [MS]" wrote:
> >
> > > You cannot share DP's between sites, or share 2.0 and SMS 2003 site roles on
> > > a machine.
> > > And Kim is correct, no SMS 2003 site role automatically installs or requires
> > > the SMS client.
> > >
> > > The other thing you may not know is that the SMS 2003 distribution point is
> > > not actually installed until the first package with content is deployed to
> > > that DP.
> > >
> > > --
> > >
> > > --
> > > --
> > > Stan [MSFT]
> > > --
> > > --
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > --
> > > --
> > > "Kim Oppalfens" <kim@xxxxxxxxxxxxxxxxxxxx> wrote in message
> > > news:MPG.1d45d410ab59e0ed98a06d@xxxxxxxxxxxxxxxxxxxxxxx
> > > >
> > > >
> > > > Don't know where you got that information, but it is incorrect.
> > > > Distribution points do not need a client installed.
> > > >
> > > > As far as the logon point goes, logon points are automatically installed
> > > > on all domain controllers if you enable logon discovery OR logon client
> > > > installation.
> > > >
> > > > If you want the logon point removed you will have to disable logon
> > > > discovery & logon clients installation in sms 2.0
> > > >
> > > > Kim Oppalfens
>
> --
> Kim Oppalfens
> MVP SMS
> Computacenter Belgium
>
.

Relevant Pages

  • Re: Strange Niggles
    ... All the machines do have the domain admin group added to the ... >> I have put in an SBS2K3 server and then connected all the machines to it. ...
    (microsoft.public.windows.server.sbs)
  • make a volume a server share
    ... share is located on a NetApp server that has only a volume. ... Is it possible to make a server share a distribution point based on the fact ... sms2003server$ account to the domain admin group, ...
    (microsoft.public.sms.admin)
  • Re: Outlook Web Access
    ... MVP - Exchange ... "Protecting the world from PSTs and brick backups!" ... back-end server that is in the same admin group as the front-end ... a mailbox on the back-end server in a different admin group, ...
    (microsoft.public.exchange.admin)
  • Cant Manage XP Machines from AD
    ... users to the local admin group. ... the server was old so we bought a new server. ... When I log in my profile comes down correctly, ... the profile they can only see certain folders: ...
    (microsoft.public.backoffice.smallbiz2000)
  • Public Folder Replication Problem
    ... Admin group A has 2 servers, one of which is a 2 node cluster. ... Admin group A contains both routing groups. ... server and select replication partners it does not replicate to them. ...
    (microsoft.public.exchange.admin)