KACE Product Support

You could run a K2000 post-installation task (after the K1000 agent has been installed) to run KBScriptRunner.exe. This will force an agent check-in with the K1000.

This is likely a multi-part solution. Andy's solution takes care of the forced check in part. On the K1 side you'd need a patching job that's set to run against new machines, possibly a rather aggressive job; which leads us to find ways to identify and group "new" machines. Smart labels would be used here, theres ~20 ways I can think of to group "new" machines. Don't forget, the easiest way to reduce the need for patching is to include the latest SP in your image/scripted install. Also consider using Microsoft MSU's (patching standalone installers) as post install tasks to keep your scripts up to date. See http://support.microsoft.com/kb/934307 for a basic intro to those.

There's a couple of ways.

There's another post in the 2000 forum that talks about the same thing.

Since then, I've been using a mix of slipstreaming and wsusoffline.

Maybe this will help.
[link]http://itninja.com/question/silent-uninstall-oracle-8-cilent0901[/link]

I use patching for adobe Flash and shockwave installs and i was trying to think of ways of just using this rather than creating a managed install.

We as a group can probably come up with 10 ways of doing something, but remember, the point of these appliances and any tool is to do it the easy way. If you have an easy solution that takes 1-2 minutes to build and 10 seconds to update and it's solid- use that. Postinstall of flash and shockwave fit the bill; that's the easy button for those products.

ORIGINAL: mattygarland

I use patching for adobe Flash and shockwave installs and i was trying to think of ways of just using this rather than creating a managed install.

We also use patching for Flash and Shockwave so when a computer is inventoried if there is no Flash Software Title found a smart label "Needs Flash Player 10 Active X" is added automatically. There's an aggressive Adobe patch schedule tied to that smart label. The schedule is set to detect and deploy all Adobe patches (Flash, Shockwave, and Reader) hourly until the smart label is gone. This works for our deployment environment (without a k2000). I suppose you could also detect a certain version of Flash instead of no Flash too.