Admin permission problem

[HTim]

We have hired a new Systems Admin. We created his account with the same
permissions as I have. All the same groups. He remotes to a server and he
can install things on it from a disk or from the internet. If he tried to
install anything from the file server he can't. I can with my logon. We
blew away his account and rebuilt it. Same problem. We built a test account
and same problem. All the old Admin accounts work fine. All the new admins
don't. We backed out the most recent updates, no change. Anyone run into
this before?

 

[HTim]

The Error I get is Windows cannot access the specified device, path, or file.
You may not have appropriate permissions to access the item.

"HTim" wrote:

> We have hired a new Systems Admin. We created his account with the same
> permissions as I have. All the same groups. He remotes to a server and he
> can install things on it from a disk or from the internet. If he tried to
> install anything from the file server he can't. I can with my logon. We
> blew away his account and rebuilt it. Same problem. We built a test account
> and same problem. All the old Admin accounts work fine. All the new admins
> don't. We backed out the most recent updates, no change. Anyone run into
> this before?

 

[Special Access]

On Mon, 23 Jun 2008 14:55:02 -0700, HTim
<HTim@discussions.microsoft.com> wrote:

>The Error I get is Windows cannot access the specified device, path, or file.
> You may not have appropriate permissions to access the item.
>
>"HTim" wrote:
>
>> We have hired a new Systems Admin. We created his account with the same
>> permissions as I have. All the same groups. He remotes to a server and he
>> can install things on it from a disk or from the internet. If he tried to
>> install anything from the file server he can't. I can with my logon. We
>> blew away his account and rebuilt it. Same problem. We built a test account
>> and same problem. All the old Admin accounts work fine. All the new admins
>> don't. We backed out the most recent updates, no change. Anyone run into
>> this before?

Did you "copy" your account, or just try and match the permissions? We
have found it works better to "copy" the account that works in AD to
make the new one. Has worked 99.9% of the time for me so far.

The only other time we saw this was when the user locked his account
while trying to enter creds after he logged on the system. It will
allow connections to the computer (via disk or i-net) but no access to
network assets.

Good luck!
Mike

 

[HTim]

The first time we copied the account. Noticed the problem amd then we blew
away the account and built it from scratch, same issue... Once remoted to any
machine I can add users ect... just like any admin but can't do any installs
from a file server.

"Special Access" wrote:

> On Mon, 23 Jun 2008 14:55:02 -0700, HTim
> <HTim@discussions.microsoft.com> wrote:
>
> >The Error I get is Windows cannot access the specified device, path, or file.
> > You may not have appropriate permissions to access the item.
> >
> >"HTim" wrote:
> >
> >> We have hired a new Systems Admin. We created his account with the same
> >> permissions as I have. All the same groups. He remotes to a server and he
> >> can install things on it from a disk or from the internet. If he tried to
> >> install anything from the file server he can't. I can with my logon. We
> >> blew away his account and rebuilt it. Same problem. We built a test account
> >> and same problem. All the old Admin accounts work fine. All the new admins
> >> don't. We backed out the most recent updates, no change. Anyone run into
> >> this before?
>
> Did you "copy" your account, or just try and match the permissions? We
> have found it works better to "copy" the account that works in AD to
> make the new one. Has worked 99.9% of the time for me so far.
>
> The only other time we saw this was when the user locked his account
> while trying to enter creds after he logged on the system. It will
> allow connections to the computer (via disk or i-net) but no access to
> network assets.
>
> Good luck!
> Mike
>

 

[Special Access]

On Tue, 24 Jun 2008 08:04:00 -0700, HTim
<HTim@discussions.microsoft.com> wrote:

>The first time we copied the account. Noticed the problem amd then we blew
>away the account and built it from scratch, same issue... Once remoted to any
>machine I can add users ect... just like any admin but can't do any installs
>from a file server.
>
>"Special Access" wrote:
>
>> On Mon, 23 Jun 2008 14:55:02 -0700, HTim
>> <HTim@discussions.microsoft.com> wrote:
>>
>> >The Error I get is Windows cannot access the specified device, path, or file.
>> > You may not have appropriate permissions to access the item.
>> >
>> >"HTim" wrote:
>> >
>> >> We have hired a new Systems Admin. We created his account with the same
>> >> permissions as I have. All the same groups. He remotes to a server and he
>> >> can install things on it from a disk or from the internet. If he tried to
>> >> install anything from the file server he can't. I can with my logon. We
>> >> blew away his account and rebuilt it. Same problem. We built a test account
>> >> and same problem. All the old Admin accounts work fine. All the new admins
>> >> don't. We backed out the most recent updates, no change. Anyone run into
>> >> this before?
>>
>> Did you "copy" your account, or just try and match the permissions? We
>> have found it works better to "copy" the account that works in AD to
>> make the new one. Has worked 99.9% of the time for me so far.
>>
>> The only other time we saw this was when the user locked his account
>> while trying to enter creds after he logged on the system. It will
>> allow connections to the computer (via disk or i-net) but no access to
>> network assets.
>>
>> Good luck!
>> Mike
>>

and when you are remoted into that computer, can you see / ping the
file server and access the shares without errors? Can he map the
drive but not install (that is, the installer won't run)? Is he
trying to run the install from a UNC or is he mapping the drive?

(gears are spinning trying to think about the last time I saw this
type of error)