![]() |
The app is not modifying it, you are. Then you have two options, build the package as a pkd or as a dmg. Then deploy it. When you run it as admin it replaces the files with admin rights to whatever files you modified or created.
Just don't make the mistake I did, and keep the user level prefs in there. I once pushed out my dock settings to about 1200 laptops....the users emailed me like crazy, and all I could say was, my bad, but its just a pref just rebuild your dock! Lesson learned the hard way LOL |
Results...
Hmm... I didn't make it clear. After I took the snapshot, i removed all references to the wireless network - both in keychain access (from the sys keychain) and from the preferred network order.
Anyway, I will soon know about the system keychain and if it replaces or modifies it. To get around the permissions issue the post-flight script i am running is a repair permissions, which takes time yes but solves the issues ;) |
Has anyone a clarifying answer to the thread starting issue as posted by tlarkin?
I'm having exactly the same problem on Leopard 10.5.3 and for me is mandatory to solve it using Applescript or terminal commands |
Quote:
look in /usr/sbin/networksetup |
Nup.
Quote:
This is a big problem for us, so i'm going to ask the Apple Dev's at WWDC tomorrow :D |
Quote:
|
I'm not sure to have explained correctly my question: I have inconsistent results from the terminal command 'networksetup', exactly as stated in the following extract from the Apple discussion forum:
************************** Loaner-2:~ tech$ sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/networksetup -getairportpower AirPort Power: Off Loaner-2:~ tech$ sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/networksetup -setairportpower on You cannot set AirPort power because all AirPort network services are disabled. Loaner-2:~ tech$ sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/networksetup -getnetworkserviceenabled AirPort Enabled Loaner-2:~ tech$ sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/networksetup -setnetworkserviceenabled AirPort on Loaner-2:~ tech$ Loaner-2:~ tech$ sudo /System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/networksetup-tiger -setairportpower on You cannot set AirPort power because all AirPort network services are disabled. ********************************* |
Quote:
I have also had issues with powering on and off the airport via command line. It could just be a bug, because I never really got it to work all that well. |
A way forward
tlarkin is right - binary's have moved as stated above. I've seen an issue with a MBA where the airport card becomes disabled because its loose, not soldered on properly or something - kinda sucks when thats the only NI you have!
Maybe ensure that you can still turn it on via the airport menu in the GUI, as if that doesn't work then time for a trip to your local store. So i've asked the ENG team at Apple about how to roll out a 'new' wireless network to clients fully back-end. The major issue for us is that out system.keychain is corrupted, and the keychains are not something you can just replace - they are encrypted and have hardware hash's and if you try to simply replace them there will be tears before bedtime. So, for us, there is a process. 1) image a mac with the same image your other users are using. 2) make the nessicary changes to the wireless 3) get the systempreferences.plist and airport.plist files from /Library/Preferences and ~/Library/Preferences (cant remmeber which one is which - maybe use some snapshot software to detect the changes - package maker is decent) 4) open keychain access and ensure that the entry for your wireless network is there. 5) open terminal, and type man security. This is where it gets tricky. You have to export the keychain item (wireless network password) in P12 format using the 'export' command 6) (for us only) - delete the system.keychain, logout then back in to generate a new one 7) copy over the preference files from before, and copy over the exported P12 file to somewhere on the users system 8) using the import switch from the security command, do an 'import' back into they system.keychain - ensuring you get the settings right. I would be more specific but I haven't tested this myself, although the guy who helped build the Apple Keychain (hehe) swears black and blue that will work. Mark |
This is the 10.4 script I used to create different setting on different wifi networks. It has been over a year since I have used it, so I can't recall exactly how effective it was.
Code:
#!/bin/bash |
Wont work
Quote:
The problem with this script is that its a once off join - the networksetup command passes another command to the airportd, which means when you run the script and 'work as advertised', but it wont save the password of the wireless network, so unless you have this script running all the time and suppressing any error messages, its probably not very effective. |
Making it usable
Quote:
|
Quote:
|
osascript -e "'tell application 'finder'" -e "activate" -e "end tell"
I believe this is how you execute applescripts from within a shell |
Quote:
|
Hah!
Nothing good comes of posting too early in the testing phase.
Essentially, everything I had blew up in my face today. *However*, I have not given up, and will post here when I have something useful to post. Meaning "other than 'Ooo, lookie what I made work except that it doesn't really work after all!'" :::grumble::: Sorry about that, guys. |
|
I got some information today that we may be migrating to WPA or something else so I was looking back into this, and I found this on google. It is an apple script, which I am not too keen on running in my environment since it runs in the gui with the user present, but I think it may be a good solution over all.
Code:
set CertName to "your.cert"Anyone here ever try this stuff? |
| All times are GMT -5. The time now is 08:01 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.
Site design © IDG Consumer & SMB; individuals retain copyright of their postings
but consent to the possible use of their material in other areas of IDG Consumer & SMB.