[QUOTE][u]Quote by: tristan_mason[/u][p]thanks for the good oil on spss. I had a go again with composer on Friday and while it made a usable installer it didn’t keep the serialization which is no good to me. I’ll have a crack at this on Monday and post the results. again thanks.
tristan[/p][/QUOTE]
I should have mentioned, this will not work with an InstaDMG setup because the activation needs to be run on each machine and is machine specific (MAC address). You can’t capture the license/serial so you will need to either deploy after imaging or make it a firstboot install.
To do a silent install of SPSS 19, download [url]http://support.spss.com/Tech/Products/Statistics/Utilities/SPSSforMacOSX/index.html[/url] (you need to have a login for support.spss.com).
then, configure the installer.properties with the following options (the file is well commented, but for a different version!):
INSTALLER_UI=silent
USER_INSTALL_DIR=/Applications/IBM/Statistics/19/ (this had to be
specified even though the instructions say it would use the default path)
LICENSE_ACCEPTED=true
### LICENSETYPE
#For site license
site=1
Then deploy with “SPSS_Statistics_Installer_Silent.bin -f
installer.properties”
Takes care of the install and licensing. You only need those 2 files, the
SPSS_Statistics_Installer_Silent.bin is the full 900MB-ish install.
However, because this exits with a non “exit 0” result, it might return an
error to your deployment tool (I use Absolute Manage) so to get around
that I just put that command in an script:
This could then be easily packaged to install with a postflight, I just haven’t done so because we’re only deploying through Absolute Manage as requested.
Yes, if your DNS srv records are correct, it should only try to use the DC’s in their site.
You can troubleshoot with some info from [url]http://support.microsoft.com/kb/247811[/url].
Any reference you see to something like _ldap._tcp.DnsDomainName, use a command in this format:
[code]dig -t srv _ldap._tcp.yourDNSdomain[/code]
You want to determine that machines in your building(s) are getting the correct DC’s from DNS and that they are part of the site you think they should be. If your infrastucture is purely AD (authentication and DNS), then you’re probably in better shape than those of us that have AD + non-AD DNS.
I made iLife and the updates for part of my Deploy Studio workflows. I mainly did this so I could have the option of iLife 08 and 09 without 2 images, but it also solves the problems you mention.
My typical DeployStudio workflow looks like:
set computer name
restore image
install iLife 08/09
Install iLife updates on first boot (these all reside in a single folder so I can just add new updates to a folder)
bind to OD
bind to AD
I was indeed building from a 10.5 machine, I did not realize that the installer had changed that much.
The only default setting I changed was the CHROOT setting in instadmg.bash. I’m glad this issue is solved, the only downside is that I have to move the Xserve that I use as buildstation to 10.6.
[/p][/QUOTE]
Can you set yourself up with a 10.6 build station running the client OS instead of using an Xserve? Seems like overkill and if you’re running any services on that box, you might not want to upgrade just for this purpose.
The LANDesk client needs to be installed on first boot. It has way too much that gets done in the scripts. I’m surprised you had it working in the past.
Run “mcxquery” command from the client and see what the output says (Leopard only).
The option key should bring up the group picker window, but that check box “allow admins to refresh….” I think is just a Leopard server thing. You might be running the Leopard WGM against a Tiger server which might be giving you that extra option. I’m not sure if it would work in that case.
I’ve been seeing this problem ever since 10.5.7 came out, I don’t think it is because of InstaDMG but I’m not 100% sure. The problem I think is because I have/had a modifed /etc/authorization which conflicted with cups changes in 10.5.7. The fix has been to add the user to the _lpadmin group:
[QUOTE][u]Quote by: giordano+mela[/u][p]hi all
can I implement magic triangle solutions with win server 2000 domains or does it work only with 2003 and later?
thanks[/p][/QUOTE]
The AD plugin can not authenticate in another forest. If this is just another domain in the same forest, you will need to specify the domain with the login name (ie. corporate\userid). If you do need cross domain auth, then you’ll need to look at something like ADmitMac.
Recent Comments