نصب برنامه روی کلاینت توسط سرور

[benyamin_p]

بدون اینکه کلاینت بفهمه
با توجه به اینکه ویندوز کلاینت xp هست
بدون پچ terminal
برنامه روی کلاینت نصب کنیم
تو یکی از تاپیکای سایت گفته شده بود
توی gp
قسمت compter or user بسته به نیازت
software setting
بعد hnstall software
اونجا add pakage
اما توی software من خالیه نمیشه چیزی هم add کرد

---

موضوعات مشابه:

• علت کیل نشدن یوزر در ras توسط nttac ( روی 2 سرور جدا از هم) ؟
• عدم اجازه اضافه کردن آیکون روی دسکتاپ توسط یوزر
• نحوه دریافت میل های روی دامین توسط میل سرور داخلی
• مشکل ست کردن آی پی سرورها روی کلاینتها توسط کاربران

---

[mkm]

بدون اینکه کلاینت بفهمه
با توجه به اینکه ویندوز کلاینت xp هست
بدون پچ terminal
برنامه روی کلاینت نصب کنیم
تو یکی از تاپیکای سایت گفته شده بود
توی gp
قسمت compter or user بسته به نیازت
software setting
بعد hnstall software
اونجا add pakage
اما توی software من خالیه نمیشه چیزی هم add کرد

شما باید client را member of domain کنید.

[mesbahsoft]

نه بابا منظور ایشون اینه که توی ام ام سی که باز کرده و داره تنظیمات گروپ پالیسی رو انجام میده نمی تونه پکیج ایجاد کنه
البته که باید کامپیوتر هایی که می خواهیم این پالیسی رو بپذیرند عضو دامین باشند ...
اما من فکر می کنم یا یوزری که باهاش کنسول رو باز کردید دسترسی نداره
وگر نه محاله که نتونید اونجا چیز جدید اضافه کنید

[SADEGH65]

جناب طباطبایی عزیز قرار بر این است که به موضوعات به این شکل در سایت لینک داده نشود .
لینکی نیز که از سایت خود داده بودید مطلب خواصی در مورد تنظیمات نداشت.


------------------

بنیامین جان منظورت در مورد خالی بودن چیست ؟(لطفا عکس قرار بدهید )

[benyamin_p]

من قعلا توی تاپیک join کردن کلاینت ها به دامین دارم مشکلی که برای join کردن به دامین هست را دنبال می کنم تا اولین ضرورتی که دوستان فرمودند برای این کار هست رفع شه یعنی کلاینت ها را عضو دامین کنم البته انگار عضو شدن ولی ....... که تو اون تاپیک دارم دنبالش می کنم
بعد از اینکه اولین مورد انجام شد می بینم اگه باز هم مشکل بود اینجارو ادامه میدم
از همگی دوستان هم تشکر می کنم که راهنمایی می کنند

[ai_samira]

آقای benyamin_p فکر میکنم شما مستقیم از طریق gpedit.msc وارد gp شده اید که software setting تون خالیه. شما باید اول وارد Active Directory Users and Computers بشید و حالا از اینجا وارد gp مربوط به کل دامین ویا OU خاصی بشید (Domain Name \ properties \ Group Policy \ Edit \ Software Setting \ Software Installation \ new \ Package) و از اینجا Group Policy رو تغییر بدید.
حالا این تنظیمات روی کلاینت هایی که عضو این دامین هستند اعمال میشه .

[patris1]

How to use Group Policy to remotely install software in Windows Server 2003

This step-by-step article describes how to use Group Policy to automatically distribute programs to client computers or users. You can use Group Policy to distribute computer programs by using the following methods:

• Assigning Software
  You can assign a program distribution to users or computers. If you assign the program to a user, it is installed when the user logs on to the computer. When the user first runs the program, the installation is finalized. If you assign the program to a computer, it is installed when the computer starts, and it is available to all users who log on to the computer. When a user first runs the program, the installation is finalized.
• Publishing Software
  You can publish a program distribution to users. When the user logs on to the computer, the published program is displayed in the Add or Remove Programs dialog box, and it can be installed from there.

Note Windows Server 2003 Group Policy automated-program installation requires client computers that are running Microsoft Windows 2000 or later.



Create a Distribution Point

To publish or assign a computer program, you must create a distribution point on the publishing server:

1. Log on to the server computer as an administrator.
2. Create a shared network folder where you will put the Microsoft Windows Installer package (.msi file) that you want to distribute.
3. Set permissions on the share to allow access to the distribution package.
4. Copy or install the package to the distribution point. For example, to distribute Microsoft Office XP, run the administrative installation (setup.exe /a) to copy the files to the distribution point.

Create a Group Policy Object

To create a Group Policy object (GPO) to use to distribute the software package:

1. Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. In the console tree, right-click your domain, and then click Properties.
3. Click the Group Policy tab, and then click New.
4. Type a name for this new policy (for example, Office XP distribution), and then press ENTER.
5. Click Properties, and then click the Security tab.
6. Click to clear the Apply Group Policy check box for the security groups that you want to prevent from having this policy applied.
7. Click to select the Apply Group Policy check box for the groups that you want this policy to apply to.
8. When you are finished, click OK.

Assign a Package

To assign a program to computers that are running Windows Server 2003, Windows 2000, or Microsoft Windows XP Professional, or to users who are logging on to one of these workstations:

1. Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. In the console tree, right-click your domain, and then click Properties.
3. Click the Group Policy tab, select the group policy object that you want, and then click Edit.
4. Under Computer Configuration, expand Software Settings.
5. Right-click Software installation, point to New, and then click Package.
6. In the Open dialog box, type the full Universal Naming Convention (UNC) path of the shared installer package that you want. For example, \\file server\share\file name.msi.
   
   Important Do not use the Browse button to access the location. Make sure that you use the UNC path to the shared installer package.
7. Click Open.
8. Click Assigned, and then click OK. The package is listed in the right pane of the Group Policy window.
9. Close the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.
10. When the client computer starts, the managed software package is automatically installed.

Publish a Package

To publish a package to computer users and make it available for installation from the Add or Remove Programs tool in Control Panel:

1. Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. In the console tree, right-click your domain, and then click Properties.
3. Click the Group Policy tab, click the group policy object that you want, and then click Edit.
4. Under User Configuration, expand Software Settings.
5. Right-click Software installation, point to New, and then click Package.
6. In the Open dialog box, type the full UNC path of the shared installer package that you want. For example, \\file server\share\file name.msi.
   
   Important Do not use the Browse button to access the location. Make sure that you use the UNC path to the shared installer package.
7. Click Open.
8. Click Publish, and then click OK.
9. The package is listed in the right pane of the Group Policy window.
10. Close the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.
11. Test the package:
    
    Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
    
    1. Log on to a workstation that is running Windows 2000 Professional or Windows XP Professional by using an account that you published the package to.
    2. In Windows XP, click Start, and then click Control Panel.
    3. Double-click Add or Remove Programs, and then click Add New Programs.
    4. In the Add programs from your network list, click the program that you published, and then click Add. The program is installed.
    5. Click OK, and then click Close.

Redeploy a Package

In some cases you may want to redeploy a software package. For example, if you upgrade or modify the package. To redeploy a package:

1. Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. In the console tree, right-click your domain, and then click Properties.
3. Click the Group Policy tab, click the Group Policy object that you used to deploy the package, and then click Edit.
4. Expand the Software Settings container that contains the software installation item that you used to deploy the package.
5. Click the software installation container that contains the package.
6. In the right pane of the Group Policy window, right-click the program, point to All Tasks, and then click Redeploy application. You will receive the following message: Redeploying this application will reinstall the application everywhere it is already installed. Do you want to continue?
7. Click Yes.
8. Quit the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.

Remove a Package

To remove a published or assigned package:

1. Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. In the console tree, right-click your domain, and then click Properties.
3. Click the Group Policy tab, click the Group Policy object that you used to deploy the package, and then click Edit.
4. Expand the Software Settings container that contains the software installation item that you used to deploy the package.
5. Click the software installation container that contains the package.
6. In the right pane of the Group Policy window, right-click the program, point to All Tasks, and then click Remove.
7. Do one of the following:
   
   • Click Immediately uninstall the software from users and computers, and then click OK.
   • Click Allow users to continue to use the software but prevent new installations, and then click OK.
8. Quit the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.

Troubleshoot

Published Packages Are Displayed on a Client Computer After You Use a Group Policy to Remove Them

This situation can occur when a user has installed the program but has not used it. When the user first starts the published program, the installation is finalized. Group Policy then removes the program.



How to assign software to a specific group by using Group Policy

You can use Group Policy to assign or to publish software to users or computers in a domain. Additionally, it is useful to be able to deploy software based on group membership. A Group Policy object (GPO) is usually applied only to members of an organizational unit (OU) to which the GPO is linked. Because a user cannot be located in several OUs at the same time, you must be able to apply Group Policy settings outside the boundaries of OUs. This article describes how to have your software deployment policy applied to users who are not in an OU.

Assign a program to a group

1. Create a folder to hold the MSI package on a server. Share the folder by applying permissions that let users and computers read and run these files. Then, copy the MSI package files into this location.
2. From a Windows 2000-based computer in the domain, log on as a domain administrator, and then start Active Directory Users and Computers.
   
   Note You can apply Group Policy settings to domains, sites, and OUs.
3. In Active Directory Users and Computers, right-click the container to which you want to link the GPO, click Properties, and then click the Group Policy tab.
4. Create a new GPO for installing your MSI package, and then give the new GPO a descriptive name.
5. While the new GPO is selected, click Edit. This starts the Group Policy Object Editor.
6. Open and then right-click Software installation in the GPO, and then click New Package.
7. You are prompted for the path of the Windows Installer file (.msi) for this package. View the network location that contains the Windows Installer file, click the file, and then click Open.
   
   Warning If the Windows Installer file resides on the local hard disk, do not use a local path. Instead, use the UNC path of the local computer to indicate the location of the installation files. A UNC path takes the form \\servername\sharename\path\filename.msi.
8. When you are prompted to choose between Assigned and Advanced Published or Assigned, click Assigned unless you have to modify the advanced options. You should now see the software package in the details pane of the Group Policy Object Editor.
9. In Active Directory Users and Computers, click the container to which you linked your GPO. Right-click that container, click Properties, and then click the Group Policy tab.
10. Click your GPO, and then click Properties.
11. Click the Security tab, and then remove Authenticated Users from the list.
12. Click Add, and then select the security group which you plan to have this policy applied to add it to the list.
13. Select your security group, and then give them Read and "Apply Group Policy" permissions.

Changes to a GPO are not immediately applied on the target computers. Instead, changes are applied according to the current Group Policy update interval. You can use the Secedit.exe command-line tool to impose GPO settings upon a target workstation immediately

[benyamin_p]

از سمیرا یک تشکر ویژه دارم به خاطر اینکه حدسشون درست بود::البته patris عزیز هم زحمت کشیدن زبان اصلیشو به طور کامل گذاشتن :: از همگی دوستانی هم که در این تاپیک برای راهنمایی من تلاش کردن تهایت سپاس را دارم

[lotfali]

راهنمايي كه دوستان انجام داده اند مربوط به مواقعي مي باشد كه end user روي سيستم دسترسي admin داشته باشد.

سوال من اينه كه چگونه كاربران نهايي مي توانند بدون داشتن دسترسي admin ، نرم اقزارهاي كه از طريق group police ، روي سيستمها publish مي شود را نصب كنند.
با تشكر