Coding, Design & GraphicsIf you are programming a script, designing a web page, building your own graphics or anything related and need to discuss it, get help and tips or general advice, then you should post your thoughts to this section.
Windows has it's own file creation and installation software that allows you to do just this,
How to create your own setup file with Microsoft Windows XP and Vista
1- Click on Start menu and then click on Run, to open RUN dialog box. (or start, search in Vista)
2- Type Iexpress and then click ok, Iexpress Wizard appears.
3- Select first radio dox (Create new self extraction directive file) and then click next.
4- Here select final result of the package and then click next.
5- In this section you can type a title for your install file, type your title and then click next.
6- If you want to confirm that the user wants to install your package, select second radio, otherwise select first radio, and then click next.
7- Here you can include a License agreement for your installation, if you want a license agreement, type your license agreement in a text file and then include file.
8- Now you can select your files in this section, click Add button to add your files and then click next.
9-if you have selected to run an installation command in step 4, here you should select your command.
10- In finished message section you can include a finish massage for your installation.
11- Click finish to create setup file.
i am trying to push out a .ini file onto everyone's c:\windows directory
i create a .bat file to say copy from the shared server location to a destination but most likely the GPO has not kicked in yet or it is all going wrong
it is common for scripts to work when you run them but not as a Startup script. When a Startup script runs there is no user. Startup scripts run with System privileges on the local computer, but with the permissions of the computer object elsewhere in the domain. The most likely cause is that the computer object (computer domain account) lacks permissions in the share. If all computers need permissions, you can grant the permissions to the domain group "Domain Computers".
Also it may be worth adding the actual filename to the end of the copy command as scripts like completeness.
One other thing is where are you deploying it in the gpo - user config or machine config and have you got the gpo running both types of script ( you can be selective so check whats selected ).
it is common for scripts to work when you run them but not as a Startup script. When a Startup script runs there is no user. Startup scripts run with System privileges on the local computer, but with the permissions of the computer object elsewhere in the domain. The most likely cause is that the computer object (computer domain account) lacks permissions in the share. If all computers need permissions, you can grant the permissions to the domain group "Domain Computers".
Also it may be worth adding the actual filename to the end of the copy command as scripts like completeness.
One other thing is where are you deploying it in the gpo - user config or machine config and have you got the gpo running both types of script ( you can be selective so check whats selected ).
its under the Machine GPO
i currently have all the computers in a nice tidy GPO but all these stupid new requests are going to do my head in if i cant start pushing files out
i have managed to do a registry key via the machine GPO which seems to work fine
i will put the full address on the end of that sapdoc.ini file and see what happens
also the 'domain computer' permission is that located in the GPO for access or somewhere else
You are running computer policies so giving authenticated users access to the gpo wont make any difference as they are run before logon when the computer connects to the domain which is why you need domain computer permissions.
You would be better doing this direct in ADS i think, we haven't introduced a WSUS server yet tho as we couldn't justify the sever cost until we go virtualised this summer but I thought they were mainly just for windows updates more than to be used like a SMS Server as was.
to check if the policy is being deployed properly you should run 'resultant set of policies' from a group policy snap in, from mmc you need the adminpak and groupadm (think thats its name ) then you can run the report on a pc and see what policies have run which have failed and for what reason.
You are running computer policies so giving authenticated users access to the gpo wont make any difference as they are run before logon when the computer connects to the domain which is why you need domain computer permissions.
You would be better doing this direct in ADS i think, we haven't introduced a WSUS server yet tho as we couldn't justify the sever cost until we go virtualised this summer but I thought they were mainly just for windows updates more than to be used like a SMS Server as was.
to check if the policy is being deployed properly you should run 'resultant set of policies' from a group policy snap in, from mmc you need the adminpak and groupadm (think thats its name ) then you can run the report on a pc and see what policies have run which have failed and for what reason.
yep wsus fully working was trying to add the reg key inside that wsus gpo but i know it will cause me problems in the long run.
the wsus server is sooo much better for our company as we have limited access for peoples internet so some PC's never used to get updates.... also the amount of bandwitdh that 100+ users take up when they us to start doing the downloads individually (512k leased line) but hopefully we will have out 2mb lease line in a few weeks and bandwidth wont be a problem
and even better now as we can control the SP3 rollout rather then our internet users trying to do it themselves and causing us problems
i am gonna give it another go before the weekend and keep this thread constantly updated with my problems as i hate group policies
need to create a setup file
Linear Mode
