Clean delete on a client?

[Hayden]

Is it necessary to remove any files when re-building and testing? Can you just reinstall over and over again safely? Is there a script to cleanly remove simian from a client?

[Allister Banks]

If you want to wipe and reload settings or certs granularly you can, otherwise for scortched-earth here's a set of instructions, assuming you used the default naming to create the package in your makefile:

https://bizappcenter.zendesk.com/entries/21812618-How-to-delete-the-BizAppCenter-client-package-from-your-Mac

Allister

On Thu, Apr 11, 2013 at 4:27 PM, Hayden <crackh...@gmail.com> wrote:

Is it necessary to remove any files when re-building and testing? Can you just reinstall over and over again safely? Is there a script to cleanly remove simian from a client?

--
You received this message because you are subscribed to the Google Groups "Simian Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to simian-discus...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Justin McWilliams]

You can reinstall over and over again.  Do note, however, that configs will not be overridden; this is intentional, so configs can be managed by a config management solution, and a shared client dmg can be created for all clients: https://code.google.com/p/simian/source/browse/trunk/postflight#182

There is also no uninstall script, but if you need to do this it should be as easy as:

  rm -rf /usr/local/munki

  rm -rf /etc/simian

  rm -rf /Library/Managed\ Installs

- Justin

On Thu, Apr 11, 2013 at 4:27 PM, Hayden <crackh...@gmail.com> wrote:

Is it necessary to remove any files when re-building and testing? Can you just reinstall over and over again safely? Is there a script to cleanly remove simian from a client?

--

[Hayden]

When you speak of configs, will removing all those directories get rid of the client-side config? Where for example is the expected 'required issuer' stored on the client?

[Justin McWilliams]

Yes. Simian client configs are all in /etc/simian and Munki client configs are in /Library/Managed Installs

[Hayden]

Alrighty, having a problem here.

I removed everything from a client, then reinstalled munki only to talk to my repo - it's now erroring out because it's searching for this manifest:

http://192.168.0.1/munki_repo/manifests/stable

Which to me, seems like simian left some kind of config behind I'm not able to find...I've wiped seemingly everything, the manifest in the ManagedInstalls.plist file is NOT set to this one above, any thoughts?

[Gregory Neagle]

Look in /var/root/Library/Preferences for an ManagedInstalls.plist.

Blow it away if found.

-Greg

[Hayden]

Thanks for the tip, didn't find anything in there - my repo is set to:

SoftwareRepoURL = "http://192.168.0.1/munki_repo";

I'm currently grepping my entire machine for "manifests/stable" - still not sure where that's coming from....

When I run sudo managedsoftwareupdate from the terminal I see:

Checking for available updates...

WARNING: Skipping invalid HTTP header: Cookie:

    Retrieving list of software for this machine...

ERROR: Could not retrieve manifest client_manifest from the server.

ERROR: Error 22: The requested URL returned error: 404

ERROR: Could not retrieve managed install primary manifest.

    No changes to managed software are available.

When I run the GUI, I see this in the /Library/Managed\ Installs/Logs/ManagedSoftwareUpdate.log

Apr 17 2013 09:47:19 -0400 Checking for available updates...

Apr 17 2013 09:47:19 -0400     Getting manifest client_manifest...

Apr 17 2013 09:47:19 -0400 WARNING: Skipping invalid HTTP header: Cookie:

Apr 17 2013 09:47:19 -0400     Retrieving list of software for this machine...

Apr 17 2013 09:47:19 -0400     Download error: http://192.168.0.1/munki_repo/manifests/stable. Failed (22) with: The requested URL returned error: 404

Apr 17 2013 09:47:19 -0400 ERROR: Could not retrieve manifest client_manifest from the server.

Apr 17 2013 09:47:19 -0400 ERROR: Error 22: The requested URL returned error: 404

Apr 17 2013 09:47:19 -0400 ERROR: Could not retrieve managed install primary manifest.

Now I'm even more confused, is one less verbose? Are they pulling from different places? Any other suggestions?

[Hayden]

Ok wow, so, the file was actually located in:

/private/var/root/Library/Preferences/ByHost

Case closed!

[Shane Pinnell]

Same issue for me... Thanks for the tip!