20. April 2012 a 07:00 | Article by John Sebald |
2 Comments
Order in a Windows domain in Adobe Reader to clients that are running Windows Vista and 7 provide, we need the following components:
HowTo This therefore includes the following points:
- Create the deployment directory
- Create local directory
- Application unpack
- Slipstream Update .msp in das Windows Installer Paket .msi
- The D:\ReaderEntpackt clean
- Processing of the msi package with Orca MSI Editor
- Lokale Testinstallation
- Adaptation of the MSI package with the Customization Wizard X
- Copy files into the software distribution
- Software Distribution with Group Policy
- Conclusion
read more…
09. November 2011 a 07:00 | Article by John Sebald |
0 Comments
Extensively tested in this HowTo is about, in a Windows domain with Windows 7 Elemente customers (Shortcuts) to the taskbar automatically via Group Policy or to attach solve. This can be realized with a PowerShell script (.ps1) and a GPO, that when the user logs, das Script started.
HowTo This therefore includes the following points:
- PowerShell script for attaching elements
- PowerShell scripts to allow testing
- PowerShell script to release of elements
- Path for x86 and x64
- Create Group Policy to distribute the PowerShell scripts
- More links
read more…
06. October 2011 a 07:00 | Article by John Sebald |
0 Comments
In a Windows Server Active Directory domain, you can take the netlogon share in creating a new user the default settings such as tray elements, Adjustment of the Start menu and much more pretend.
The netlogon share is under its own domain \\FQDN\netlogon (%logonserver%netlogon) to find. It will default on a Windows server to install the Active Directory creates role.
If the profile is available in the release, and a newly created user logs on for the first time on a client-W7, the adjusted profile is loaded automatically. The profile does not exist, is the local Default profile loaded.
Important to know is, that Microsoft uses different versions of roaming profiles:
- Windows XP corresponds to the profile folder name "Doe"
- Windows Vista corresponds to the profile folder name "Mustermann.V1"
- Windows 7 corresponds to the profile folder name "Doe.V2”
Now we must do the following:
read more…
19. July 2011 a 07:00 | Article by John Sebald |
0 Comments
In order for Windows 7 Clients with Group Policy (Benutzerkonfiguration > Einstellungen > Systemsteuerungseinstellungen > Drucker)Network- Shared Printers and successfully assign, have the point-and limitations-point enabled and will be adjusted accordingly. Thus, in active User Account Control (Active is recommended!) the driver loaded as in the execution of the GPO and installed the printer.
The policy is available at Computerkonfiguration > Administrative Vorlagen > Drucker > Point-and-Point-Einschränkungen to find. There, the following settings must be made:
read more…
08. July 2011 a 07:00 | Article by John Sebald |
2 Comments
Following initial situation is represented: A new network printer was delivered and I have this on Windows SBS 2003 R2 with the latest PCL5 driver installed and enabled. So far, no problem. After that I have with the Group Policy (Benutzerkonfiguration > Einstellungen > Systemsteuerungseinstellungen > Drucker)a new TCP / IP printer and added that by targeting the appropriate Windows XP and Windows 7 Clients can be distributed.
So far so good. First, I have the GPO to a test computer by gpupdate updated, so the printer would have to be actually installed. Far. Okay I thought, as any administrator I check the event log on the client first. In fact, I'm right in the application log at the source "Group Policy Printers' find anything:
The user "192.168.xx.xx" setting item in the GPO "Default printer {4A5E0823-D333-4E69-B2E1-990B03BA1738}" was not taken, because an error with error code "0×80070706 The print processor is unknown." This error was suppressed. occurred.
read more…
