Deploying Chrome extension using Group Policy

IT administrators can set Chrome policies to install our Chrome extension on their corporate-managed computers. Chrome extension is installed on computers silently and users cannot uninstall it.

Message is visible only in developer mode

Note: This article provides instructions for Windows users. If you are Mac or Linux user, please follow Google instructions how to setup Chrome policy.

1. There are two types of policy templates available, an ADM and an ADMX template. You’ll want to verify which template type you can use on your network (ADM templates are designed for Windows XP / Server 2003, whereas ADMX templates are for Windows Vista onwards.). These templates show which registry keys you can set to configure Chrome, and what the acceptable values are. Chrome looks at the values set in these registry keys to determine how to act.

2. Download Google Chrome templates and documentation.

Transferring the FSMO Roles via Ntdsutil

To transfer the FSMO roles from the Ntdsutil command:
Caution: Using the Ntdsutil utility incorrectly may result in partial or complete loss of Active Directory functionality.

C:\>ntdsutil
ntdsutil: roles
fsmo maintenance: connections
server connections: connect to server XYZ
Binding to XYZ …
Connected to XYZ using credentials of locally logged on user.
server connections: quit
fsmo maintenance: transfer schema master
fsmo maintenance: transfer domain naming master
fsmo maintenance: transfer rid master
fsmo maintenance: transfer infrastructure master
fsmo maintenance: transfer pdc

use the following command to check the status.

netdom query fsmo

How to: Make Secondary Domain Controller the Primary, when primary fails.

This will help you change your secondary domain controller to primary when your primary fails.

 

Step 1: one

Open CMD on the secondary domain, at prompt type Ntdsutil and press enter.

Example: C:\windows>ntdsutil
ntdsutil:

Step 2: Two

Once complete type: roles and press enter.
you will see-
fsmo maintenance:

Step 3: Three

Then type: connections and press enter.
you will see-
server connections:

Now type the name of the secondary server you are trying to make primary.
Example-
server connections: connect to myserver 
it will say connected using local user.

 

Step 4: Four

Next step type q.
server connections: q

Now we are going to seize the FSMO.
type:
seize domain naming master 
seize PDC 
seize RID master 
seize schema master

Step 5: Five

from start—> click run and enter dsa.msc

right click the domain that shows and select Operations Master.

From here promote your domain.

How to configure and verify the DHCP relay for EX-series switches

SUMMARY:

This article provides information on how to configure and verify the DHCP relay for the EX-series switches.

SYMPTOMS:

How to configure and verify the DHCP relay for the EX-series switches.

CAUSE:

Configuring IRB Interfaces

Integrated routing and bridging (IRB) interfaces enable a switch to recognize which packets are being sent to local addresses so that they are bridged whenever possible and are routed only when needed. Whenever packets can be switched instead of routed, several layers of processing are eliminated. Switching also reduces the number of address look-ups.

Note: In versions of Junos OS that do not support Enhanced Layer 2 Software (ELS), this type of interface is called a routed VLAN interface (RVI).

To configure the routed VLAN interface:

1. Create the VLAN by assigning it a name and a VLAN ID:
   [edit]
user@switch# set vlans support vlan-id 111
2. Assign an interface to the VLAN by specifying the logical interface (with the unit statement) and specifying the VLAN name as the member:
   [edit]
user@switch# set interfaces ge-0/0/18 unit 0 family ethernet-switching vlan members support
3. Create the subnet for the VLAN’s broadcast domain:
   [edit]
user@switch# set interfaces irb unit 111 family inet address 10.0.0.0/8
4. Bind a Layer 3 interface with the VLAN:
   [edit]
user@switch# set vlans support l3-interface irb.111

   Note: If you are using a version of Junos OS that does not support ELS, you create a Layer 3 virtual interface named vlan

    

Recovering System Booted From Backup JUNOS Image

This article describes the issue of a system booting from the backup root partition after a file corruption occurs on the primary root partition. This article is targeted for SRX and EX devices at this time.

1. Problem

EX switches and SRX firewalls running Junos Release 10.4R3, or later, have added resiliency based on the “resilient dual-root partition”, which if the switch detects a corruption on the primary root file system, it boots from the alternate root partition.

When this occurs, you are notified in two ways: Alarm and Warning Banner

1.1. Alarm

The following alarm message is generated:

user@switch> show chassis alarms
1 alarms currently active
Alarm time Class Description
2011-02-17 05:48:49 PST Minor Host 0 Boot from backup root

1.2. Warning

***********************************************************************
**                                                                   **
**  WARNING: THIS DEVICE HAS BOOTED FROM THE BACKUP JUNOS IMAGE      **
**                                                                   **
**  It is possible that the primary copy of JUNOS failed to boot up  **
**  properly, and so this device has booted from the backup copy.    **
**                                                                   **
**  Please re-install JUNOS to recover the primary copy in case      **
**  it has been corrupted.                                           **
**                                                                   **
***********************************************************************

2. Cause & Solution

It is likely that the file system became corrupted due to a sudden power loss, or ungraceful shutdown of the system.

Repairing the primary partition when it is corrupted:

• When the primary partition detects a corrupt, the device boots from the backup partition; which then becomes the active partition. Remember that after every successive reboot, the system will try to reboot from the current active partition.
• You can repair the primary partition, without any downtime. No reboot is required after running the following commands.  However the Alarm and Banner will be displayed.

_{Note: As long as both of the partitions are healthy, there is no issue with running the switch on either of them. You only have to ensure that both the partitions are healthy, so that fail over can be done transparently between the two partitions, in case of any file corruption.}

How do I enable Remote Desktop connections to Windows using Group Policy on a Windows Server domain?

A. With the rename of Terminal Services to Remote Desktop Services in Server, you also have new locations for the Group Policy settings to enable Remote Desktop.

1. Open the Group Policy Object (GPO) you’ll use for the remote desktop settings.
2. Navigate to Computer Configuration, Policies, Administrative Templates, Network, Network Connections, Windows Firewall, Domain Profile.
3. Double-click Windows Firewall: Allow inbound Remote Desktop exceptions.
4. Set this to Enabled and add the addresses that can connect. This could be * for all IP addresses, specific subnets, or localsubnet for only the local subnet.
5. Click OK.
6. Navigate to Computer Configuration, Policies, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Connections.
7. Double-click Allow users to connect remotely using Remote Desktop Services, set it to Enabled, then click OK.
8. Close the Group Policy object and make sure it’s linked to the required locations.

Below is the report of my GPO that enables Remote Desktop. It will also enable Remote Desktop on Windows XP, Windows Server 2003, and later systems.

First blog post

This is your very first post. Click the Edit link to modify or delete it, or start a new post. If you like, use this post to tell readers why you started this blog and what you plan to do with it.