Network drive disconnected???

  • Thread starter Thread starter René Vézina
  • Start date Start date
R

René Vézina

Hi !

My situation:

1. I use GPO machine for "Map Network Drive" with "Scripts Sartup -
Start-Machine.bat"
2. This batch file contains:
net use f: \\%serveur_reference%\%drive_f%
net use H: \\%serveur_reference%\%drive_h%
3. %serveur_reference%, %drive_f% and drive_h% have the value in
"HKLM\SYSTEM\CurentControlSet\Control\Session Manager\Environnement"
4. %drive_f% = Dépot_Global$
%drive_h% = Dépot_Global$\%Computername%
5. This GPO aplying correctly
6. "Dépot_Global$" is a "share folder" with full security rights for
"Acces_Global" group
7. "Acces_Global" contains computer object members for access this network
storage space

When I go to the "My computer", for the "Hard Disk Drive" section:
- Network drive disconnected ( F: )
- Network drive disconnected ( H: )

What happened?

A computer object is a security principal, that just as with user, I can
give permissions for ressources with a security group memberships.

Thanks in advance!

René
 
Hi Rene,

What happens if you connect the drives using a logon script instead of the
startup script? I'm guessing that there is something going on with the
context they are mapped in, but not sure off the top of my head. I'll do
some digging, but I'm curious to see what happens if you do it per user
instead of machine.

--
 
Hello Mike,

I'd get my network drive with GPO logon script applied to the OU user.
Result:
- Dépot_Global$ on 'server-a.my.domain.org' ( F: )
- Computername on 'server-a.my.domain.org\Dépot_Global$' ( H: )
This test was already.

If Microsoft says that: <A computer object is a security principal> then I
should obtain the same result with this concept.

Our need for is allocated a network storage space according to the function
(application) for the computer.
Note: Properties for Dépot_Global$
- Share permissions: Everyone (read), Authenticated Users (Full
Control, Change, Read)
- Security: Group -> Acces_Global (Full Control, Modify, Read &
Execute, List Folder
Contents, Read, Write)

Thanks Mike.
René
 
Ok, that's what I suspected. What if you click on the "disconnected" drive
once a user has logged on when the startup script runs? Does it reconnect,
or does it continue to show as disconnected? A long time ago I saw an issue
like this and I'm trying to find the details to see what the answer was, but
it seems like it had to do with the machine context vs. user context.
 
Hello Mike,

When I click on the "disconnected" drive, it continue to show disconnected.
I can see the data.

All the users based on one "OU": Code_Users.centre.my.domain.org

The computers distribued on diferrent "OU":
Ordinateurs.S_Info.centre.my.domain.org,
Ordinateurs.S_Fin.centre.my.domain.org,
Ordinateurs.S_Rmat.centre.my.domain.org,...

I believe that you marks a point... :)

Is there a solution???

Thanks a lot Mike.

René
 
Hello Mike,
In my second test. As you said, when I move the computer object in the same
"OU" as the user object. When the GPO - Startup script runs, the drives
are connect.

Thus the <machine context vs. user context> give different results.

I'm waiting for your response.

Thanks a lot.

René
 
Hi Rene,

If I understand correctly, by moving the computer into the same OU as the
User accounts, it works as a startup script.
Showing the drive as connected.

OR

If you connect the drive in a login script it works, showing the drive as
connected.

BUT

If you run it as a startup script with the computer account in different OU
than the User account it maps the drive, but shows as "disconnected". But
if you click on it, it works and you're able to access the data...

So it seems like it works in all scenarios, but it shows as "disconnected"
which might be misleading to users...

Is that all accurate? Where are you setting the scripts at? Separate
policies on each OU?
 
Hello Mike,

Excuse for the long time before the response, I were in vacancy last Friday.


Mike Shepperd said:
Hi Rene,

If I understand correctly, by moving the computer into the same OU as the
User accounts, it works as a startup script.
Showing the drive as connected.
Exactly!


OR

If you connect the drive in a login script it works, showing the drive as
connected.
Click to expand...

Yes, login script for User accounts and computer object in different OU .
BUT

If you run it as a startup script with the computer account in different
OU than the User account it maps the drive, but shows as "disconnected".
But if you click on it, it works and you're able to access the data...
Exactly!

So it seems like it works in all scenarios, but it shows as "disconnected"
which might be misleading to users...

Is that all accurate? Where are you setting the scripts at? Separate
policies on each OU?
Click to expand...
I have different GPO for each OU:
- User configuration OU for Code_Users.centre.my.domain.org (Security
Setting, Folder redirection, ...)
- Machine configuration OU for Ordinateurs.S_Info.centre.my.domain.org
(System scripts, Assigned application,...)
- Machine configuration OU for Ordinateurs.S_Fin.centre.my.domain.org
(System scripts, Assigned application,...)
- Machine configuration OU for Ordinateurs.S_Rmat.centre.my.domain.org
(System scripts, Assigned application,...)

Thanks Mike.
 
Back
Top