Office 2010/Office 2013 CLI Product Activation

Many times, Open License versions of Office 2010/2013 will install without ever prompting you for a product key, defaulting to the 30 or 60 day trial mode. Couple of quick commands that can tell you what’s up with a user’s Office installation.

1. Determine Your MS Office Configuration

32bit OS:
Office 2010 (32bit) – C:\Program Files\Microsoft Office\Office14
Office 2013 (32bit) – C:\Program Files\Microsoft Office\Office15

64bit OS:
Office 2010 (32bit) – C:\Program Files (x86)\Microsoft Office\Office14
Office 2010 (64bit) – C:\Program Files\Microsoft Office\Office14
Office 2013 (32bit) – C:\Program Files (x86)\Microsoft Office\Office15
Office 2013 (64bit) – C:\Program Files\Microsoft Office\Office15


2. Check MS Office Activation Status

  • Open an administrative level command prompt.
  • Change directory to the Office14/Office15 folder:

cd “C:\Program Files\Microsoft Office\Office14”

  • Run the query status command:

cscript ospp.vbs /dstatus

  • The license name and/or license description gives the license type for Office, while license status shows activation status of Office 2010.


3. Input Activation Key

cscript ospp.vbs /inpkey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

4. Force Key Activation With Microsoft

cscript ospp.vbs /act

5. Grab a beer.

Configure SSLVPN on Fortigate with Local Authentication

NOTE: These steps were performed on a Fortigate 60-D. The concepts are the same across all devices, the menus vary just slightly between models.

1. Configuring a VPN User Account

Log into the Fortigate and go to User & Device > User > User Definition and create a new user account:


2. Create Web Portal For End User

The main thing to note on this screen is the IP Pool. It will use a default SSLVPN pool as the addresses it uses for incoming VPN connections. You can modify the scope/subnet in Firewall Objects > Address > Addresses if the range conflicts with your network. Add a tagline, theme, layout as you prefer. It really depends on your users and not overloading them with options. On the larger Fortigate units, you can create multiple portal pages for different groups of users. For smaller customers, they typically use it for a VPN connection, and not much else.


3. Create a Security Policy

I typically create two security policies to accommodate the VPN traffic. Obviously, you can widen or narrow what your granting access to. In this example we are giving the remote user access to the entire LAN behind the Fortigate.

First Policy:

This is essentially the NONAT policy between the VPN subnet and destination internal network.

Second Policy:

Under the Configure SSL-VPN Authentication Roles section, you can click the Create button to add the vpnuser we created initially. You can of course add a group and select the portal that user/group will see.


4. Certs, Timeouts, DNS

Confirm your IP Pool, Self-Signed cert is fine for now, and make sure your DNS servers specified are correct for your internal network. You’ll mostlikely want your users to resolve internal hostnames correctly.


5. Grab a beer

Configuring Cisco 2960X-48TS-L FlexStack

NOTE: All switches intended for the stack must be on the same version of IOS code. If your switch is revisions behind what is current, I recommend updating them as your first step. Easier to do it now while you have the chance, than once it’s in production.

1. Remove module covers on rear panel before powering on. Insert FlexStack modules into the respective slots and tighten the securing screws. Cable stack as follows:

2 Switches
switch1/stack1 > switch2/stack1
switch1/stack2 > switch2/stack2

2. Attach console cable to switch1, open up a terminal window, and plug in the switch power to switch1 only. You can watch it run through it’s boot sequence. At first boot, it will attempt to run through the basic configuration which is fine. I typically select:

Hostname:  sw-customer-01
Enable Secret:  ************
Enable Password:  ************ (must be different than secret)
Virtual Terminal Password (aka Telnet):  ************ (I typically remove this later, using SSH only)
Configure SNMP Management Network?  No
Enter interface name used to connect to the management network from the above interface summary:  FastEthernet (I typically use the mgmt port on the front, use whichever port you prefer)
Assign an IP/Subnet Mask
Enable as a cluster command switch?  No
Select Option 2 to save create config


3. Check to make sure the Flex-Stack Module is registering in switch1. Run the following command:

sw-customer-01# show switch stack-ports
      Switch # Port 1  Port 2 
      -------- ------  ------ 
         1      Down    Down

^^Showing ‘Down’ is ok, it is still registering that the module is installed in switch1.^^


4. Power on switch2. Wait a few minutes until the switch is fully booted. You can keep your console cable connected to switch1 this entire time. Periodically re-running the command from step 4. Once switch2 is fully booted, your output should read:

sw-customer-01# show switch stack-ports    
      Switch # Port 1  Port 2    
      -------- ------  -----      
         1       Ok     Ok      
         2       Ok     Ok

^^This confirms both switches and both stack module ports on each switch is functioning properly^^


sw-customer-01# show switch stack-ring    
      Stack Ring Speed        : 20GB    
      Stack Ring Configuration: Full    
      StackRing Protocol      : FlexStack

^^This confirms the speed of our backplane, the redundancy of our cabling and the method in which we have stacked the switches^^


sw-customer-01# sh ip int b

^^The output of this command should show you that both switches and all 96 ports are manageable from a single master switch location. The master switch is signaled by the greet ‘MAST’ light on the front. There should only be one master per stack.^^

5. Grab a beer.



Throughput – Dramatically increased, taking advantage of that aggregate 20GB backplane stack connection.

Expandability – Run out of ports? Hot add a new switch to the FlexStack at any time, and it should be automatically detected and bundled with the others. Remember, same IOS code and you can only stack a total of 4 switches together.

Management – Gotta love a single point of management for all of your switches. One IP address to access and manage everything in the stack.