Re: Config Manager 2007.. packages.. programs.. command .. can spe

Hi Mark,

Kim is right. It would be the System account of the Workstation, not the
server and it would have no O: drive mapping in that account context so I
suspect that is why your package is failing. The workstation system accounts
probably don't have an O: mapping.

Just thinking of a few ways around this...

1. Assign a System Startup Script that maps the O: drive for the system
context on computer startup. Haven't tested this but in theory it should
work.

2. Set up a static DNS mapping for a certain (bogus) name and point it to
the IP of the source server? Then if by chance you change the source server
out AND assign a new IP then you just need to update the DNS entry to point
to the correct IP. You would then use the bogus name in your commandline
path.

3. Assign all of your users Admin rights and run the package in User
context. :) (kidding!)


Thanks,
-Jeff



"markm75c@xxxxxxxxx" wrote:

On Nov 20, 11:05 am, "Kim Oppalfens [MVP]" <""Kim dot Oppalfens
\"@google mail.com"> wrote:
markm...@xxxxxxxxx wrote:
On Nov 19, 8:39 am, "Garth" <S...@xxxxxxx> wrote:
yes it is but keep in mind that the ConfigMgr client uses the Computer
account to access data therefore it is that account that needs access to
your o:\

<markm...@xxxxxxxxx> wrote in message

news:9a12c275-374b-414e-8272-e5130082e0aa@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

In the past with sms 2003.. i always put the path like .. \\server\apps
\app1\install.exe for the command line..
Is it possible with 2007.. to simply specify o:\path here?
I tried it in one case.. but received the error on the client saying
it couldnt find the source file.
Its the case in all situations that we will not have definition files
etc.. we just have an apps setup folder which resides on an O: drive
(which will never change in letter)...
Thanks- Hide quoted text -
- Show quoted text -

Would that be the computer account of the CM 2007 server i'm
assuming? As of now.. if they try the advertisement it gives the
error about couldnt find required files (when using the O: path).. but
if i use the \\server\apps path.. it works fine.. if O: and \\server
\apps path are the same.. why would it be a rights issue?

It probably isn't a rights issue, your most likely mapping this o drive
using a login script, so localsystem has no knowledge of the o drive.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMShttp://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_manage...- Hide quoted text -

- Show quoted text -

I should mention.. my goal here was to provide a path that wouldnt
change.. ie: if i have to move the setup files to another server or
another subfolder due to space issues.. i'd like this path to somehow
stay the same (i've already done this once and had to go through all
50 packages and change the path names...

.

Relevant Pages

  • Re: different security context in SQL Analyzer and Job
    ... Without mapping any logins, it would go through the default ... other server and permissions to whatever you were running. ... I add the map for the SQL Agent NT account in the linked ...
    (microsoft.public.sqlserver.security)
  • Re: DCOM, threads, impersonate?
    ... My server can be compared to an opc-server, it connects to one or many ... "Why not use a specific account .." ... Other clients connection to the same device ... impersonate in a thread which is not created in the context of an inbound com ...
    (microsoft.public.vc.atl)
  • syncronise workstation / server logon while not in domain
    ... windows 2003 server - context being a guy logs onto his xp (local ... account only) and then wants to access a file server which has ...
    (microsoft.public.windows.server.security)
  • Re: Weird problem
    ... When I try mapping from server A, to a share in B, I get error ... Mapping to same share from other computers are fine. ... domain account. ... I can access server B from any other PC or server remotely. ...
    (microsoft.public.windows.server.networking)
  • Re: Re-Post - "the trust relationship between this workstation and the
    ... "the trust relationship between this workstation and the primary domain ... only problem is adding a new user account on the station. ... Client computer must use STRICTLY the INTERNAL DNS server which can ... Attr: subschemaSubentry ...
    (microsoft.public.windows.server.active_directory)
Loading