Despiste 8: Obtener el listado de certificados de una máquina remota
This time I leave a script to obtain the list of certificates installed digital equipment in the warehouse of a remote machine. There is no simple way to do this with powershell, so we kicked enough head and browsing a lot of forums I've been chasing parts of other scripts and pieces of code in other languages \u200b\u200bto create this little (although I think useful) script. The script takes as parameters the hostname to connect to (-computerName) and warehouse to connect (-store). Valid options for the store are:
Thursday, January 21, 2010
Hypothesis On Dancing Raisins
"Root" certificate store for trusted root 
"My": for personal certificate store "CA" for the certificate store intermediate CAs
"TRUST": to the certificate store business confidence
- is necessary to launch the script with administrator privileges on the remote machine.
- I would also tell you that the script is in alpha stage and is unstable, so that I can assure you 100% that works every time, but to me it has worked.
Here you have the link so you can download the script: Get-RemoteCerts.ps1
Tuesday, January 12, 2010
Buy Jordan Basketball Warm Ups Tops
Despiste 7: Aumentar el periodo de evaluación de Windows Server 2008
Surely I am not alone Windows 2008 servers that mounts to do their testing before going on to higher. The problem with having these servers is that if we comply with the law we must install the corresponding license, but the truth and the truth is that nobody pays much grace having to duplicate licensing costs simply by having a platform for the beast.
As you may know, the evaluation period of Windows Server 2008 (any version) is 60 days, but if we execute the command
Surely I am not alone Windows 2008 servers that mounts to do their testing before going on to higher. The problem with having these servers is that if we comply with the law we must install the corresponding license, but the truth and the truth is that nobody pays much grace having to duplicate licensing costs simply by having a platform for the beast.
As you may know, the evaluation period of Windows Server 2008 (any version) is 60 days, but if we execute the command
slmgr.vbs-rearm, we reset the evaluation period by up to three times more have an evaluation period of 240 days. 
Does Yogurt Help Gonorrhea?
Despiste 6: Cambiar el canal de licencia de un Windows XP
Well, after some time if you write anything, it's time to get to "Curran" a bit:). This may be one of the classic problems to which most Windows administrators have faced in some time, the reactivation of a Windows XP license after a cloned or virtualization. Let's see, I put a little background so you can have a complete picture of the problem that I have had to face this time. As I have said on occasion, I have to manage a VMware platform larger or smaller, which also uses VMware View. Well, as expected had to come a time in which they begin to virtualize user desktops. Virtualization If these desks are made from scratch, this would not cause any problems, we launched the converter, we tell the machine you want to import, we expect a "little bit" and ... voila, virtualized PC and ready for use. Where is the problem?, Because they obviously do not live in an ideal world and that desktop virtualization is calling for the PCs of users who already have installed, configured and customized to your liking. If you have bad luck we can find in the following case:
Microsoft offers three licensing channels:
OEM
a reduced cost license you get when you buy a computer with Windows preinstalled. This license is associated with the hardware and can not be reused on other hardware different.
References:
determine the channel's license
CD
Extended information channels
Well, after some time if you write anything, it's time to get to "Curran" a bit:). This may be one of the classic problems to which most Windows administrators have faced in some time, the reactivation of a Windows XP license after a cloned or virtualization. Let's see, I put a little background so you can have a complete picture of the problem that I have had to face this time. As I have said on occasion, I have to manage a VMware platform larger or smaller, which also uses VMware View. Well, as expected had to come a time in which they begin to virtualize user desktops. Virtualization If these desks are made from scratch, this would not cause any problems, we launched the converter, we tell the machine you want to import, we expect a "little bit" and ... voila, virtualized PC and ready for use. Where is the problem?, Because they obviously do not live in an ideal world and that desktop virtualization is calling for the PCs of users who already have installed, configured and customized to your liking. If you have bad luck we can find in the following case:
The PC user has a WindowsXP preinstalled (OEM) and we want to virtualize 
. At this point I would make a small section and clarify a bit the Microsoft licensing channels.
. At this point I would make a small section and clarify a bit the Microsoft licensing channels. Microsoft offers three licensing channels:
OEM
a reduced cost license you get when you buy a computer with Windows preinstalled. This license is associated with the hardware and can not be reused on other hardware different.
- Retail (RTL) , is the license that we acquired when we purchased the original software for clean installations or upgrades. There are certain restrictions on the movement of license if you have purchased a software upgrade.
- Volume License (VLK) , is typical corporate license where a product key can only license a large number of computers.
- Well, the problem arises when we installed Windows XP with an OEM installation CD and after having passed the sysprep and have virtualized (for the clones feel the same) try to license it under a VLK or RTL. The solution to this problem is simply to get a cd of the proper discharge channel and do a system repair from the installation CD, ie starting from the CD and starting the installation process, but instead of crushing the old installation, we say that the repair. Be careful not to enter the repair console that offers the first setup.
Be careful in the case of virtual machines that VMware SCSI controller that configures the default is not supported by the program Windows XP installation, so you will have to add the driver manually.
References:
CD
Extended information channels
Subscribe to:
Posts (Atom)