Thursday, May 23, 2013

Activate Windows 7 Pro with MAK Key via SCCM 2012 task sequence

Objective: Whenever a Windows 7 Pro computer is deployed via SCCM 2012 task sequence, I would want Windows to be auto activated.

Solution: 1. In SCCM 2012 console => Task Sequences=> edit task sequence => apply windows settings => product key: type in Windows 7 Pro MAK key here  (if you don't have MAK key get one),

2. add run command line => command line: cscript.exe c:\windows\system32\slmgr.vbs /ato

3. start in:  c:\windows\system32



Note: Make sure when you add the Run Command Line, place it at the bottom of the list or at least right after "Setup Windows and Configuration"  .....This solution worked for me and I hope it will for you too!



then windows is auto activated once deployed.

Can I delete files in the %windir%\Installer directory?

Along the same lines as removing items from the Windows component store to save space, I have recently seen a couple of questions come in about the Windows\Installer directory. This is a hidden system directory; it is used by the Windows Installer service to cache installer data files for various applications. Over time, this directory will grow and can eventually take up an amount of space that might cause pressure on thinly provisioned storage.

So, the question usually asked is: Can I safely remove the files in this directory? The answer is flatly: No. So let's talk about why this is a bad idea.

First, it is not supported. If you remove files from this directory and have issues, you may need to reinstall the application to get back to a good state. Therefore, that would suck for both you and the engineer that needs to deliver that message.

Second is the overall idea that you really should not remove items in the Windows directory. We build and test our software based on the existence of specific files and directories. When those files and directories don't exist, bad things can and will happen. However, that is a generalization that usually upsets many people so let's be more specific. This particular directories job is to act as a cache location for Windows installer based applications. It holds stripped down versions of the Windows installer data files. During application install, update of the application or application removal, this directory is used by the application to confirm the existence of previously installed items to determine the next steps the installer needs to take. The files are different from machine to machine, so if you expect to delete the files in the directory and then copy them over from another machine, that would be incorrect. Removing items from here could cause you to have application crashes, or worse, require the reinstallation and patching of the application.

The proper way to alleviate space pressure in this directory is to uninstall any unneeded applications.
I hope that this makes sense and you can see why removing files from this directory can cause you unneeded pain. Overall, this is similar to the advice I have given in the past when it comes to removing items from the component store...just don't do it. Plan your future space requirements based on your operating system and application needs and you can alleviate many of these types of issues before they occur.

Wednesday, May 15, 2013

Last time a computer authenticated to domain

Objective: Needed to know when a computer has last logged on to the domain? I basically want to clean up a load of old computer accounts in AD.

Solution: "dsquery computer -inactive 24 -limit 0 >>C:\Lastlogon.txt"

Note: 24 being the number of weeks not logged into, and pipe the result to the C drive location.

Thursday, May 2, 2013

Cisco Switch 3750 POe went bad, not giving power to the VOiP Phones.


Here was what I did in summary to fix the issue.

 

1.       Pinged Site BB from Site PK was successful.

2.       Went to Site BB to look at the switch, a lot of ports has no light to them.

3.       In cisco switch, within the bad interface did a “Shut” command(gave me a power failure error, I forgot what it said exactly) then a “no shut”  (nothing happened and was at Administrative Down”

4.       Restarted the cisco switch “connected via USB Console”
    
      5. Ran into a looping error messages that I couldn’t get out of (The only happens when VoIP Phones are plugged into the Cisco 3750 POe switch)


6.       Called Cisco to get a replacement switch (arrived at 4 hours later)

7.       In the old switch I was able to Telnet in so I ran the “Show power inline” command it tells you which ports are bad, apparently all ports got bad for some reason after switch rebooted & having the VoIP phone plugged into the switch port (only 6 cisco phones were plugged).
 


8.      
8.       Switch arrived then  loaded the configuration from the old switch (used TFTP to saved the backup of old switch config), now it’s  working.

Friday, April 26, 2013

Windows 7 TFTP: error code 11 received - 18025 or %Error opening tftp://

Objective: Copy my switches/routers running-config to TFTP server(which is on my laptop)

Error: TFTP: error code 11 received - 18025

Attempts: Login to another workstation that's on the same LAN, DLed the TFTPd64 application and successfully utilizes the TFTP  to copy the running-config file of the switch. Then I know it's SOMETHING on my computer.

Solution: That something is the "WinAgents TFTP Service 4" service started automatically, so I had to disable that service. WOOHOO the TFTP is working again!


Note: The solution fits my environment, so it may helped you out and it may not. Which I hope it will.

Thursday, April 25, 2013

Steps to configure Cisco Console, Telnet and Auxiliary port passwords

Follow these steps to configure console passwords.

Note: Before performing this test, ensure that you have an alternate connection into the router, such as Telnet or Dial-in, in case there is a problem logging back in to the router.

Step 1. From the privileged EXEC (enable) prompt, enter configuration mode ((config)) and then switch to line configuration mode ((config-line), by issuing the following commands:

Note: Notice that the prompt changes to reflect the current mode.
router#conf t 
!--- Enter configuration commands, one per line.
End with CNTL/Z. 
router(config)#line con 0 
router(config-line)#

Step 2. Configure the password, and enable password checking at login.
router(config-line)#password 
router(config-line)#login

Step 3. Exit configuration mode.
router(config-line)#end
router#
%SYS-5-CONFIG_I: Configured from console by console

Note: Do not save your configuration changes until your ability to log in has been verified.

Step 4. Verify the configuration.

Examine the configuration of the router to make sure that the commands have been properly entered by issuing the show running-config command.

To test the configuration, log off the console with the exit command and log in again, using the configured password to access the router.
router#exit
router con0 is now available
Press RETURN to get started.

Step 5. Save your configuration.
router#write memory





Perform these steps to configure Telnet passwords.

Note: Before performing this test, ensure that you have an alternate connection into the router, such as console or dial-in, in case there is a problem logging back in to the router.

Step 1. From the privileged EXEC (or enable) prompt, enter configuration mode (or (config)) and then switch to line configuration mode ((config-line)), by issuing the following commands:

Note: Notice that the prompt changes to reflect the current mode.
router#conf t
!--- Enter configuration commands, one per line.
End with CNTL/Z.
router(config)#line vty 0 4
router(config-line)#

Step 2. Configure the password, and enable password checking at login.
router(config-line)#password 
router(config-line)#login

Step 3. Step 3. Exit configuration mode.
router(config-line)#end
router#
%SYS-5-CONFIG_I: Configured from console by console

Note: Do not save your configuration changes until your ability to log in has been verified.

Step 4. Verify the configuration.

Examine the configuration of the router to make sure that the commands have been properly entered, by issuing the show running-config command.

Test the configuration by making a Telnet connection to the router.

This can be done by connecting from a different host on the network, but you can also do so from the router itself by Telnetting to the IP address of any interface on the router that is in an up/up state as seen in the output of the show interfaces command.
router#telnet 

Step 5. Save your configuration.
router#write memory





Follow these steps to configure Auxiliary (AUX) port passwords.

Note: before performing this test, ensure that you have an alternate connection into the router, such as console or Telnet, in case there is a problem logging back in to the router.

Step 1. From the privileged EXEC (or enable) prompt, enter configuration mode ((config)) and then switch to line configuration mode ((config-line)), by issuing the following commands:

Note: Notice that the prompt changes to reflect the current mode.
router#conf t
!--- Enter configuration commands, one per line.
End with CNTL/Z.
router(config)#line aux 0
router(config-line)#

Step 2. Configure the password, and enable password checking at login.
router(config-line)#password  
router(config-line)#login

Step 3. Exit configuration mode.
router(config-line)#end
router#
%SYS-5-CONFIG_I: Configured from console by console

Note: Do not save your configuration changes until your ability to log in has been verified.

Step 4. Verify the configuration. Examine the configuration of the router to make sure that the commands have been properly entered by issuing the show running-config command. Test the configuration by making an inbound or outbound connection to the line.

Step 5. Save your configuration.
router#write memory

Thursday, April 18, 2013

Upgrading ConfigMgr 2012 from Evaluation version (Enter SCCM 2012 License Key)

In System Center 2012 Configuration Manager it is really easy to upgrade an installation that was made using the Evaluation option when you installed it to a fully licensed installation by simply entering the Product key.

It is done by using the “Configuration Manager Setup” which can be found on the Start menu or by simply running install from the installation source.

When the setup starts select the “Perform site maintenance or reset this Site” in the following wizard you can convert the installation from an evaluation to a fully licensed installation.
Here is a step-by-step guide:

  1. Start Configuration Manager Setup either from the start menu or the installation source.
  2. Select the “Perform site maintenance or reset Site” option


3. Then you get the option to “Convert from Evaluation to Full Product Version. Enter your 25-character product key:”



4.  In the next screen accept the license agreement

5. Finished!







  1. Then you get the option to “Convert from Evaluation to Full Product Version. Enter your 25-character product key:”