|
| | | Forum Newbie
Group: Forum Members
Last Login: 7/24/2008 3:43:41 PM
Posts: 2, Visits: 8 |
| | I am fairly new to Prism, but have been installing software in multiple user environments for years. When we install software with items like registration or user specific setup, we typically install the software as a test user and then copy the test user's profile to the default profile. This enables every new user to the computer to pull down the registration and specific setup so it is already setup for him/her. With Prism, I can still copy over the test profile as part of a package. However, if the user has already logged onto a machine he/she will not pull down the default profile. Is there a way I can make the default profile apply to users who already have a profile using a prism package? Thank you for your help!!! |
| |
| | | 
Supreme Being
Group: Moderators
Last Login: 2/12/2011 11:11:06 PM
Posts: 742, Visits: 1,211 |
| With Prism Packages, there's no need to copy things to the Default Profile. Our packager automatically creates a user portion and a machine portion in the package. When you deploy the package through the Prism Console as a Package Task, the machine portion runs and the user portion runs for the user who is currently logged in. Whenever another user logs in, they get the user portion added to their settings. It's that simple.
New Boundary Technologies Support
support@newboundary.com |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 7/24/2008 3:43:41 PM
Posts: 2, Visits: 8 |
| | Unfortunately it is not that simple. Let us take iTunes for example. We created a package for iTunes that would be specific for our district. We wanted to be able to easily tell users how to back up their iTunes and we wanted to prevent them from doing such things as downloading movies anything over Rrated. We set these items in the iTunes setup as a user (expecting that Prism would install these settings as we packaged for all users) and then packaged the installation. What happens when pushing out the package is that it installs the settings for one user and then if a second user logs on, it removes all those user specific settings and the user then has everything set to default (not as it is packaged). We are currently experimenting with scripts that will install software for all users (not just the first user to log on) with specific settings and not just simply install the software. Thank you for your assistance!! |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 10/13/2008 1:31:01 PM
Posts: 1, Visits: 764 |
| | Here is what I would do...Once you have all the settings applied under the user profile correctly, I would create the path for default user (C:\Documents and Settings\Default User") and then I would simply copy the profile from the one created during the packaging process. You may use a variable so that it resolves to the current user, but I would copy that into default user and you should be all set. Eric Hirst
Eric Hirst |
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 8/12/2010 11:07:09 AM
Posts: 1, Visits: 3 |
| | I'm having the same problem. I already tried the suggested default user step described, but I'm having problem gettin the setting to hold in the package. When I setup the default user as described manually and then test it out, it works as planned. When I create the package, the settings do not stay and thus do not hold for each user. I think my next step will be to create an operating system specific package but being a complete n00b, I'm not entirely sure how to do that. |
| |
| | |
Supreme Being
Group: Moderators
Last Login: 2/12/2011 11:11:06 PM
Posts: 742, Visits: 1,211 |
| Another thing to add on to what Eric was saying is when creating a variable inside of the packager you will want to make sure that you uncheck the checkbox that says "Value should be the same for all users of the same computer".
If you leave this checked on the variable you created, the first user that logs on to get the package will be what it resolves to for the rest of the users which could be causing the problems you are seeing. If you uncheck that checkbox then each user should have the variable resolve correctly according to their profile.
If you are having any more problems with this I recommend calling into our support department so our support team can look at the package to see what is causing these problems.
Our number is 612-379-1851
New Boundary Technologies Support
support@newboundary.com |
| |
|
|