Hi Alan. Thanks for the detailed explanations. Regards, Rudi. Thanks for this explanation. Now the behaviour is clear. But I think it would make life easier, if the settings of any profile selected for login would make it into the user's login profile for each successful login.
Thank you all very much for the replies, and I'm glad that the discussion turned into something robust. You can get "close", but not exactly as you describe. If you delete all your per-user profiles, and have the System Login Profile configured with the defaults you want and "Save profile on successful login" unchecked, the users should all refer to the System Login Profile and never save a per-user version.
What you're not getting with that is "save whatever changes the latest user entered back to the System Login Profile". The System Login Profile is always going to have exactly the settings the administrator configured. No, that's not what is expected. As soon as you change the username entered into the "Username" field, you've effectively "reset" and reloaded the list of available login profiles.
This happens because, at least in the Novell Client for Windows 7, the login profiles available. Ah I see. When I do the runas command, I think that it fails when it starts the first msi I have yet to figure out what this means Is the Executable on a Network Share? These thoughts may not be shared by either Novell or any rational human. When I push out the OS I have the exe going with it.
I thought that I might be able to come up with a script to execute the exe at first login or something But that doesnt help if I can't get it to runas admin. How are you executing the runas? I have the preagent during the image load process as well and it is already logged in with the administrator account so don't need to do a runas.
Well, we have a nice mix of machines. So creating images for everyone would be crazy. Its nice because it detects all of the hardware automatically and installs the appropriate drivers. So with that, we don't have the option to create an image with the agent already installed. And sadly the agent is not Sooo we are looking for a way to get the agent installed on the first boot.
I can get Tivoli to put the Agent. Any suggestions are appreciated. I think the term "silent" has different definitions. I think of silent as a totally invisible, no traces of the install in the GUI. Others may think of it as an install that does not prompt the user to do anything, which is what the -x switch seems to do. The user most definitely sees action going on. The old msi installer was entirely invisible. It would be sweet to have such an option again It wasn't designed for that.
IIRC there is an enhancement request open for this, but I don't know if this enhancement made it into TID It works with the Now I just need to be able to detect when the install actually finishes The only catch is, there is no visible way to tell that it has finished, in order for you to reboot.
As the reboot is necessary, and with scripting you need a sense of where exactly you are in the process, I've had to get creative to make a single standalone installer. Are you able to install the Agent as the very last step in your script? Then leave the agent reboot the wks by itself. That's what we do. That could be done. The thing is, we like to fully customize everything about an app install, that includes settings, firewall, post-installation reboots, etc.
So creating an installer for First, sure, you can do it in a batch, but the public installation switches on the preagent installer are FAR from silent or quiet. We need a totally invisible installation, and we will control the reboots and post installation behavior with our software deployment infrastructure, in our case, BigFix. OK, here's the long and short of it. I'm going to write a cool solution with the specific details and actual code, but I'm a little stoked about getting this all working so I want to write about it : - install.
It's sort of unfortunate that we were forced to bend over and re-engineer the installation process, but it is what it is. The Cool Solution is forthcoming. You must use the -q switch. That's the quiet switch. True the switch is not "totally" quiet. So your batch can proceed to the next steps. And you can monitor a file, reg key, or whatever to know when the client has ended its install. We dont have firewalls on workstations so that's a big peace not needed to manage. Sign up today to participate, stay informed, earn points and establish a reputation for yourself!
Log in. Is there a switch or param setting for batch files to run an uninstall string silently? Asked 6 years ago views. Scripting Silent Uninstall Commands Batch. My two cents Posted by: dunnpy 6 years ago. Posted by: EdT 6 years ago. If all else fails, save Y to a text file, eg Y.
Sign in to vote. Monday, January 13, PM. Your clients will need to resolve the SCCM servers Edited by fern. Saturday, January 18, PM. It not going to help to manually install the CM! I would work on that issue before trying to install the CM12 client.
0コメント