Skip to main content

Hi everyone, we are using a Login script to mount Windows Network shares

this works fine if we run it by selfservice,

[STEP 1 of 4]
Executing Policy Domain Login
[STEP 2 of 4]
Running script DomainLoginScript...
Script exit code: 0
Script result:
paedML Windows 4.2 Anmeldeskript macOS 12.x Monterey Angemeldeter Benutzer: xxx Meine AD-ID: uid=1668260950(xxx) gid=1023584668(xdom\\Domänen-Benutzer) groups=1023584668(xdom\\Domänen-Benutzer),12(everyone),62(netaccounts),394028230(xdom\\G_Projekte),720414751(xdom\\G_Lehrer_BKS),646384096(xdom\\G_Internet),778572741(xdom\\Office365_CreateGroups),1126509300(xdom\\G_Lehrer),701(com.apple.sharepoint.group.1),1585533833(xdom\\OCTO_user_internet) Gruppenzugehörigkeit: Lehrer Home-Pfad: mldata/Benutzer/Lehrer/BKS/xxx Tausch-Pfad: mldata/Tausch/BKS Mounte Laufwerke: - Home Mounting sp01.xdom.schule.paedml Mounted file server <mountpoint>/Volumes/xxx</mountpoint> - Tausch Mounting sp01.xdom.schule.paedml Mounted file server <mountpoint>/Volumes/BKS</mountpoint> - Schüler Mounting sp01.xdom.schule.paedml Mounted file server <mountpoint>/Volumes/BKS-1</mountpoint> - Programme Mounting sp01.xdom.schule.paedml Mounted file server <mountpoint>/Volumes/pgm$</mountpoint> Fertig!
rSTEP 3 of 4]
rSTEP 4 of 4]

 

but it fails by running it with loginTrigger

Executing Policy Domain Login
Running script DomainLoginScript...
Script exit code: 0
Script result:
paedML Windows 4.2 Anmeldeskript macOS 12.x Monterey Angemeldeter Benutzer: xxx Meine AD-ID: uid=1668260950(xxx) gid=1023584668(xdom\\Domänen-Benutzer) groups=1023584668(xdom\\Domänen-Benutzer),12(everyone),62(netaccounts),394028230(xdom\\G_Projekte),720414751(xdom\\G_Lehrer_BKS),646384096(xdom\\G_Internet),778572741(xdom\\Office365_CreateGroups),1126509300(xdom\\G_Lehrer),701(com.apple.sharepoint.group.1),1585533833(xdom\\OCTO_user_internet) Gruppenzugehörigkeit: Lehrer Home-Pfad: mldata/Benutzer/Lehrer/BKS/xxx Tausch-Pfad: mldata/Tausch/BKS Mounte Laufwerke: - Home Mounting sp01.xdom.schule.paedml Could not mount distribution point "sp01.xdom.schule.paedml" There was an error mounting the file server at sp01.xdom.schule.paedml. Will attempt again. Mounting sp01.xdom.schule.paedml Could not mount distribution point "sp01.xdom.schule.paedml" There was an error mounting the file server at sp01.xdom.schule.paedml. Giving up. - Tausch Mounting sp01.xdom.schule.paedml Could not mount distribution point "sp01.xdom.schule.paedml" There was an error mounting the file server at sp01.xdom.schule.paedml. Will attempt again. Mounting sp01.xdom.schule.paedml Could not mount distribution point "sp01.xdom.schule.paedml" There was an error mounting the file server at sp01.xdom.schule.paedml. Giving up. - Schüler Mounting sp01.xdom.schule.paedml Could not mount distribution point "sp01.xdom.schule.paedml" There was an error mounting the file server at sp01.xdom.schule.paedml. Will attempt again. Mounting sp01.xdom.schule.paedml Could not mount distribution point "sp01.xdom.schule.paedml" There was an error mounting the file server at sp01.xdom.schule.paedml. Giving up. - Programme Mounting sp01.xdom.schule.paedml Could not mount distribution point "sp01.xdom.schule.paedml" There was an error mounting the file server at sp01.xdom.schule.paedml. Will attempt again. Mounting sp01.xdom.schule.paedml Could not mount distribution point "sp01.xdom.schule.paedml" There was an error mounting the file server at sp01.xdom.schule.paedml. Giving up. Fertig!
_____________________________________________________________________________________________________________________

have you any idea whats the difference?

The login script may be running too early; adding a delay may help.

https://community.jamf.com/t5/jamf-pro/how-to-wait-for-desktop-to-be-ready/m-p/195224/highlight/true#M184012

https://community.jamf.com/t5/jamf-pro/how-to-wait-for-desktop-to-be-ready/m-p/195222/highlight/true#M184010

This second poster recommends using this at the top of the (bash) script, it will cause the script to wait until the Dock is running.

while true; do
myUser=`whoami`
dockcheck=`ps -ef | grep [/]System/Library/CoreServices/Dock.app/Contents/MacOS/Dock`
echo "Waiting for file as: ${myUser}"
sudo echo "Waiting for file as: ${myUser}" >> /var/log/jamf.log
echo "regenerating dockcheck as ${dockcheck}."

if [ ! -z "${dockcheck}" ]; then
echo "Dockcheck is ${dockcheck}, breaking."
break
fi
sleep 1
done

 

The login script may be running too early; adding a delay may help.

https://community.jamf.com/t5/jamf-pro/how-to-wait-for-desktop-to-be-ready/m-p/195224/highlight/true#M184012

https://community.jamf.com/t5/jamf-pro/how-to-wait-for-desktop-to-be-ready/m-p/195222/highlight/true#M184010

This second poster recommends using this at the top of the (bash) script, it will cause the script to wait until the Dock is running.

while true; do
myUser=`whoami`
dockcheck=`ps -ef | grep [/]System/Library/CoreServices/Dock.app/Contents/MacOS/Dock`
echo "Waiting for file as: ${myUser}"
sudo echo "Waiting for file as: ${myUser}" >> /var/log/jamf.log
echo "regenerating dockcheck as ${dockcheck}."

if [ ! -z "${dockcheck}" ]; then
echo "Dockcheck is ${dockcheck}, breaking."
break
fi
sleep 1
done

 


Hello,

we have tested the workaround but it didn´t solve this issue.

our sript will not run.

 

Reply


Terms & ConditionsCookie settings