<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta content="MSHTML 6.00.2900.3354" name="GENERATOR">
<style title="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body ocsi="x">
<div dir="ltr"><font face="Tahoma" color="#000000" size="2">About 90% of our local accounts are created using Casper. The other 10% are created just because the tech happens to be sitting at the computer already, so they just make the account. The only bug/issue
we've had is creating accounts right after imaging that do not have a password (we do this for some of the primary school aged kids). To work around this, I just used the jamf command line in a script that ran after imaging and it worked fine (select 'at
reboot' for the script properties in the JSS). I didn't need to do anything other than delete the account creation from the AutoRun job and instead add the script to the configuration with it's properties set to 'at reboot'. There is apparently something
with Leopard about creating a user with no password on Firstrun according to JAMF Support where instead of it being an empty password, it puts a password hash in there. We also run MS office and NeoOffice and have had no problems as long as you created your
office packages with the correct rights, which you'd have problems with anyways no matter how you create your accounts if the rights were wrong.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">One FYI is that Leopard won't update the login window as the new accounts are created like Tiger did. We also use the pictures/buttons login window so teachers can say 'click on the butterfly'.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">That's interesting to hear about MS Office crashing with AD accounts. We used to have the majority of our users on mobile accounts in Apple OpenDirectory but abandoned that as we just had too many problems. We were
looking at starting to test making AD-based accounts on our Leopard computers with the better AD support in Leopard.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">-John</font></div>
<div>
<div class="BodyFragment"><font size="2">
<div class="PlainText"><br>
-- <br>
John Wetter<br>
Technology Support Administrator<br>
Technology & Information Services<br>
Hopkins Public Schools<br>
952-988-5373<br>
john_wetter@hopkins.k12.mn.us</div>
</font></div>
</div>
<div id="divRpF404357" style="DIRECTION: ltr">
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> casper-bounces@list.jamfsoftware.com [casper-bounces@list.jamfsoftware.com] On Behalf Of Slutzky, Ben [bslutzky@mph.net]<br>
<b>Sent:</b> Wednesday, September 03, 2008 8:58 PM<br>
<b>To:</b> Casper List<br>
<b>Subject:</b> [Casper] Creating Local Accounts w/ Policies (& MS Office)<br>
</font><br>
</div>
<div></div>
<div><font face="Arial"><span style="FONT-SIZE: 12px">Hi,<br>
We need to create a local account for ~100 Macs ASAP, preferably right after image deployment. I know the built-in method of using a policy has just been suggested on another thread. Has anyone had
<i>any</i> problems with creating a user through a policy? And specifically, can anyone say for sure whether Office 2004 (or another version) works from an account created that way? (We’re avoiding AD logins because of Office crashing)<br>
<br>
Thanks in advance!<br>
<br>
Ben Slutzky</span></font> </div>
</body>
</html>