LogonStudio is a free program that allows users to change their Windows 7, Vista and XP logon screens. It comes with several logon screens to choose from, along with thousands that are available online from Web sites such as WinCustomize.com.
http://www.stardock.com/products/Logonstudio/
LogonStudio is a free program that allows users to change their Windows 7, Vista and XP logon screens. It comes with several logon screens to choose from, along with thousands that are available online from Web sites such as WinCustomize.com.
4 Comments
In this tutorial we are trying to tell an application not to save to the program files as its restricted and to save to the all users or per-profile directory. To achieve this you first need to download and install Microsoft Application Compatibility Toolkit (ACT) this tool is a very powerful tool and can be used to create custom patches and settings and apply them as needed. Link provided below:
http://www.microsoft.com/downloads/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971&displaylang=en Once installed, you need to run the Compatibility Administrator. Once loaded Under "Custom Databases" you will see a database. Right click and select "create new" -> "Application Fix". It will then ask to name the "program to be fixed" this will show up in application manager aka add and remove programs aka appwiz.cpl. Once you have located the program. Once you press next dont worry about the Operating system mode and select next. The additional compatibility modes can be used if you wanted to change resolution etc. The next menu asks for "compatibilty fixes" you can add options such as "run as administrator", In this example we want to redirect files so we want "LUAredirectFS". If you contrinue with the prompts, it will ask you other options that are not important in this example. It will then load the application as a test run. After the application has launched it should bring up information on the files and directories used. In this case it tells us to use %appath%\APPLICATION NAME\FILE\app.dll if you wanted to be safe you can press the [COPY] button and rename the path to %appath%\Application Name\file so everything in that file location will get redirected. Once all this is done and you have saved the *.sdb file you then can install it on the destnation machine by doing the following from the command promt (CMD): sdbinst "File.sdb". There are switches such as -u to uninstall and -q for silent etc. sdbinst command will give you the commands you can use. In this example, we are trying to deploy Microsoft Visio 2003 with Group Policy aka GPO.
Reference: http://windowsdevcenter.com/pub/a/windows/2005/03/22/deploying_office.html One simple way of deploying Office to your client machines is to copy the entire contents of the Office CD to a shared folder on your file server. For example, you might copy the CD files to the folder C:\Office on server TEST220 and then share this folder as Office. Now if you wanted to deploy Office to all the client computers in the Sales organizational unit (OU), you could create a new GPO called Install Office and link the GPO to the Sales OU. Then to deploy Office to computers in the Sales department, you would do the following:
If the package that you are trying to install contains a serial number you can prepare the install file by running the setup.exe file with a "/a" command. Example: Start -> run -> CMD or Start then type CMD in the search bar then when you see "cmd" right click and "run as administrator". Navigate to the directory the CD is copied to or type something like this: (D being the shared drive name) "D:\LOCATION\SOFTWARE\VISIO\Setup.exe" /a You should then be prompted with the location to store the MSI package that GPO needs to install the product. Troubleshooting: "No package in the software installation data in the Active Directory meets this criteria" The added package initially does not appear, but will eventually show up after an F5 refresh or after exiting/re-editing the GPO -- however the package will never install on client machines. The only cure here that I found is to recreate the GPO from scratch; even exporting and importing settings into a new GPO does not work. Special thanks: http://www.questconsultantsllc.com/blog/gpo-software-distribution "There is no software installation data object in Active Directory" 1) you have check the permission on the file to allow full access to the file 2) "authenticated" users have full control over the location of the .msi file both with share permissions and NTFS permissions. 3) check in your domain controller security policy if there are any policies defined that state that you cannot install .msi files across the network Special Thanks: http://www.experts-exchange.com/OS/Miscellaneous/Q_21998415.html |
AuthorIm a Network Administrator for a school. I have a strong interest in education and how education is taught. I teach students about the insides of computers on the rare occasion and teach many teachers about computers and how ICT can be used giving advantage to students learning. I'm also interested in Music, History, Ancestry, Science, Electronics etc. Hope you enjoy my blogging. Archives
August 2016
Categories
All
|