3 Replies Latest reply on Oct 15, 2008 12:44 PM by mrgui

    Safeboot - general question

      I'm just starting to work with Safeboot version 5.x and am trying to figure out how to model our deployment.

      Right now I'm not clear on the correlation between a safeboot user and a safeboot machine.

      For instance, I see that when I run the install set on a client computer, Safeboot creates an entry in the machine group area using the client computer's windows name.

      I'm not clear how the entry in Safeboot based on the client computer's windows name relates to entries in Safeboot based on user names.

      For instance, is Safeboot keeping track of things based on the computer itself (and using the computers entry in the machine group area) or is Safeboot keeping track of things based on user names.

      Thanks.
        • 1. RE: Safeboot - general question
          Note that we're using Windows XP workstations in a non-domain enviroment.

          The typical configuration is one computer assigned to one user. The computer will have two local windows admin accounts (for tech support staff) and one non-admin account (for the enduser).
          • 2. RE: Safeboot - general question
            challiwag
            What you would normally do in a safeboot deployment is have a machine group thast contains the majority of your machines. You would assign all the users that could possibly use these machines to the group, then you create the install set and roll out.
            You could one to one map the users to machines but it would be a pain to do for lots of users.

            Configuration can be based on both users and computers seperatly.
            Users are usually pulled in via "connection manager" which looks in active dircectory, but as you have stated you dont have AD, you can just enter the users manually into the console and assign them to groups.
            • 3. RE: Safeboot - general question
              You could also manually create the machine registrations and assign the users prior to software install on the clients.

              Another method would be to have a batch job (or custom executable) kick-off the SafeBoot installer (without auto-restart; include sbadmcl.exe and sbadmdll.dll in fileset), then pass control back to the script utility to prompt for user ID(s). Once script has list of users, it could register its hostname as a placeholder and assign users to it. The script should then initiate a reboot.

              Once the machine boots back up, it will discover the unused registration, activate it, and pull down the associated users.