#211558 - 2016-06-01 04:54 PM
kixtart and mapping drives Windows 10 pro x64 - FIXED
|
vivithemage
Fresh Scripter
Registered: 2016-06-01
Posts: 19
Loc: Minnesota
|
So I seem to be having an issue with mapping drives with windows 10 pro x64.
I echo'd out errors to see what was happening, and it would say the drive is already mapped, even after rebooting with only C mapped. So I unmapped all drives prior to the mapping script and it would still not map drives, or throw any errors, just return 0.
I can manually map the drives, and access the shares. It's also only occasionally not working, which makes it the most difficult to troubleshoot. Everything else in KIX completes fine. I have other Windows 10 x64 PC's that map no problem, always.
UPDATED:
Well, I found the fix, my kix32.exe file was set as run as administrator under compatibility mode. I unchecked that, and everything worked as it should!
Edited by vivithemage (2016-06-17 04:05 PM)
|
Top
|
|
|
|
#211562 - 2016-06-01 08:32 PM
Re: kixtart and mapping drives Windows 10 pro x64
[Re: Lonkero]
|
vivithemage
Fresh Scripter
Registered: 2016-06-01
Posts: 19
Loc: Minnesota
|
UAC disabled, users are local admins.
|
Top
|
|
|
|
#211563 - 2016-06-01 08:50 PM
Re: kixtart and mapping drives Windows 10 pro x64
[Re: vivithemage]
|
ShaneEP
MM club member
Registered: 2002-11-29
Posts: 2125
Loc: Tulsa, OK
|
Have you actually checked that the computer doesn't think the drives are really being used? Maybe run something like this in your script to get a log of what drives it thinks are mapped.
shell '%comspec% /c net use > c:\drives.txt' Or maybe try unmapping all drives right before mapping.
|
Top
|
|
|
|
#211564 - 2016-06-01 08:57 PM
Re: kixtart and mapping drives Windows 10 pro x64
[Re: ShaneEP]
|
vivithemage
Fresh Scripter
Registered: 2016-06-01
Posts: 19
Loc: Minnesota
|
When I mentioned that I unmapped all the drives, I had this above the mapping portion:
USE * /DELETE
|
Top
|
|
|
|
#211566 - 2016-06-01 10:22 PM
Re: kixtart and mapping drives Windows 10 pro x64
[Re: Allen]
|
vivithemage
Fresh Scripter
Registered: 2016-06-01
Posts: 19
Loc: Minnesota
|
It is a log on script. I can also run it after the log in of course.
|
Top
|
|
|
|
#211567 - 2016-06-01 10:52 PM
Re: kixtart and mapping drives Windows 10 pro x64
[Re: vivithemage]
|
Glenn Barnas
KiX Supporter
Registered: 2003-01-28
Posts: 4396
Loc: New Jersey
|
My login script provides a ton of diagnostic info. If you're willing to download and add it to your Netlogon share, it should provide enough info about the environment to possibly identify the problem without modifying your current script. See the link in my sig and browse to Products / Administrators Toolchest.
PM me with the following info and I'll create a basic config file for you to eliminate the learning curve and provide you with a 30-day demo license key (if needed): # of domain controllers in your environment (4 or less requires no license). List of resources to map - drive, UNC Path, Group(s) to control mapping (if any) Do you want to unmap drives prior to mapping? Any drives to exclude from the unmapping process?
If you can reproduce this with a specific user, update that user's profile to run the new script. Create a debug file in their user profile folder and debugging will be enabled automatically.
The debug file will identify the system environment, all groups the user is a member of, the OU that the user and computer are in, and much more. Then, for each resource being mapped the status of the authorization logic (group, site, OU, etc. memberships) and result of the mapping command will be logged. If it fails to map, this should point to the cause.
Welcome to KORG, BTW!
Regards,
Glenn
BTW - a client in Australia had an issue with no mapping on 3 of 200+ machines - by running this we were able to determine that the environment was corrupt during logon due to a system fault.
_________________________
Actually I am a Rocket Scientist!
|
Top
|
|
|
|
#211568 - 2016-06-01 11:00 PM
Re: kixtart and mapping drives Windows 10 pro x64
[Re: Glenn Barnas]
|
vivithemage
Fresh Scripter
Registered: 2016-06-01
Posts: 19
Loc: Minnesota
|
As an example, I imaged a PC with fresh windows 10, logged in as myself, as a domain admin, and it could not map them, although it completed. But on my other Win 10 PC, worked/mapped fine.
Error 85 "the local device name is already in use"
Then I add USE * /DEL and I get a return of 0 "The operation completed successfully"
but still no mapped drive. I will PM you Glenn.
Edited by vivithemage (2016-06-01 11:00 PM)
|
Top
|
|
|
|
#211570 - 2016-06-01 11:31 PM
Re: kixtart and mapping drives Windows 10 pro x64
[Re: Allen]
|
vivithemage
Fresh Scripter
Registered: 2016-06-01
Posts: 19
Loc: Minnesota
|
I actually did, no luck.
|
Top
|
|
|
|
#211579 - 2016-06-02 06:03 PM
Re: kixtart and mapping drives Windows 10 pro x64
[Re: Lonkero]
|
vivithemage
Fresh Scripter
Registered: 2016-06-01
Posts: 19
Loc: Minnesota
|
What is the token issue?
We have nothing else mapping, we have used kixtart for mapping for the last 7-8 years.
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 329 anonymous users online.
|
|
|