How to connect to a EC2 instance using Powershell

Hi guys, I don’t exactly know why but apparently there are no articles out there, with a good step by step guide to connect from your local pc to a Windows Server 2012 R2 instance hosted on Amazon AWS on EC2, this short article aims to fill this gap:


  • This article assumes some knowledge of AWS, the EC2 service and of Windows Server 2012 but nothing is complicated and I’ve added many links with large documentation
  • The Powershell comunication uses on the WinRM protocol, therefore  it needs a specific port reachable 5985 TCP  on the server (be advised, the default transport protocol will be the insecure HTTP).
  • The WinRM service is enable by default on WIN2012 R2 but the default Windows Firewall configuration is to allow connections on the 5985 port only from the same subnet of the machine, therefore we need to login to the machine using RDP an modify the default configuration of that firewall rule.
  • If your pc (the client !) is not part of the domain of the remote server you need to add the remote server into the list of your trusted hosts on YOUR pc (covered below).


  1.  Deploy the VM with Windows Server 2012 ( docs )
  2. Modify the security group of the instance, adding a rule to open the port 5985 TCP from your IP/ or from anywhere ( docs )
  3. Wait a few minutes for the machine to boot up completely and then connect to it using the Remote Desktop protocol (RDP), aka the usual way to connect to win istance on EC2 ( docs )
  4. Modify the Windows firewall configuration to allow incoming connections to the port 5985 from any ip (or as you please 🙂 ), to do so you can : Control Panel -> Windows Firewall -> Advanced Settings -> Inbound Rules -> “Windows Remote Management (HTTP-In)” where the profile is PUBLIC (make sure to choose the right one !) -> Properties -> Scope -> Remote IP Addresses -> Any IP Address (or know better ! )


    Use this simple Powershell command:
    Set-NetFirewallRule -Name “WINRM-HTTP-In-TCP-PUBLIC” -RemoteAddress “Any”

  5. Reboot the Windows Firewall service ( don’t ask me why, but sometimes the rules are not picked up until a reboot of the service, I’ve witnessed that myself ) (docs)
  6. Then make sure that the WinRM protocol is working correctly on the server machine running this comand in a shell (not really needed, just to make sure it works)  Enable-PSRemoting –force

  7. Then move to your local machine and make sure the WinRM service is working here as well, in a privileged shell:
    Start-Service -Name Winrm
  8. Then add the remote host as a trusted host, running this command into a privileged shell :
    SetItem WSMan:\localhost\Client\TrustedHosts Value “”
    or, possibly smarter maybe not super secure, use a wildcard :
    SetItem WSMan:\localhost\Client\TrustedHosts Value “*”

  9. Then connect to the remote machine using one of the various options provided by powershell such as :
    Enter-PSSession -ComputerName “” -Credential $(Get-Credential)
    Inserting the login credentials of the remote machine when requested to ( docs )


The WinRM service can be configured server side to use the more secure HTTPS on port 5986 or a COMPATIBLITY MODE running on port 80, used usually for firewall related issues ( docs).

Older versions of Windows have different requirements to set up Powershell Remoting / WinRM ( docs ).

And, obviously, this guide is generazible to many other IaaS services (Azure, Digial Ocean).

Hope this helps somebody !


Guide: Intel 82573L gigabit ethernet with Ubuntu 11.04 and fix PXE-E05

hello guys,

big post today. I’ve finally updated my Ubuntu machine to the latest version 11.04 Natty Narval…everything works out pretty well execpt for the wired ethernet controller… I’m using the

“Intel Corporation 82573L Gigabit Ethernet Controller”

this controller isn’t manageable via the usual Ubuntu Network Manager nor it’s listed in the output of the ifconfig and it’s status is unclaimed

$ sudo lshw -C network
*-network UNCLAIMED
description: Ethernet controller
product: 82573L Gigabit Ethernet Controller

There is no problem at all with Windows 7 or my old Ubuntu release 8.x , the card is fully working.

In the meantime I have noticed a long time recurring error (it was there for a long time before the  11.04) at the computer boot time (BIOS time),  looking like a bootstrap error :

“Initializing Intel Boot Agent GE v.1.2.28 PXE-E05: LAN adapter’s configuration is corrupted or has not been initialized. The Boot Agent cannot continue.”

the linux log messages helped me a little

$ dmesg | grep e1000
[ 0.267811] pci 0000:01:00.0: reg 18 32bit mmio: [0xee100000-0xee10ffff]
[ 0.268161] pci 0000:00:01.0: bridge 32bit mmio: [0xee100000-0xee1fffff]
[ 0.346430] pci 0000:00:01.0: MEM window: 0xee100000-0xee1fffff
[ 0.346978] pci_bus 0000:01: resource 1 mem: [0xee100000-0xee1fffff]
[ 0.918428] e1000e: Intel(R) PRO/1000 Network Driver – 1.0.2-k2
[ 0.918432] e1000e: Copyright (c) 1999-2008 Intel Corporation.
[ 0.918486] e1000e 0000:02:00.0: Disabling L1 ASPM
[ 0.918510] e1000e 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.918554] e1000e 0000:02:00.0: setting latency timer to 64
[ 0.918766] e1000e 0000:02:00.0: irq 29 for MSI/MSI-X
[ 0.990779] e1000e 0000:02:00.0: PCI INT A disabled
[0.990781] e1000e 0000:05:00.0: (unregistered net_device): The NVM Checksum Is Not  Valid                                                                                                                                                                                                                 [0.990788] e1000e: probe of 0000:02:00.0 failed with error -5

I have also been able to understand that this problem is not limited to the 82573L card but is common for a large number of intel ethernet cards (that is why you can easily understand the driver’s blacklisting in the old linux distributions) : 82563, 82566, 82567, 82571, 82572, 82573, 82574, 82577, 82578, 82579,  or 82583 -based.

So what is going on ? It looks like that the nework adapter’s (82573L) EEPROM is broken, unfixed and a little messed up, (error PXE-E05) this problem creates a checksum error for the NVM (The NVM Checksum Is Not Valid) that breaks the Ubuntu driver loading  therefore the eth0 alias is not created and there isn’t a manageable ethernet adapter for the Ubuntu network manger.

Windows simply doesn’t check the NVM checksum, it uses the card anyway and everything works fine.

IMHO Intel messed up a little with the 82573 controller there are too many similar errors out there, it seems it happens when there is a sudden power outage during LAN card bootime…totally nonsense !

Anyway, we need to fix this !!! As you can easily understand the idea behind this guide will work  for many others Intel controllers from the same family: I’m unable to test them but it’s probably worth giving it a shot !

And here it’s the guide…it’s not as long as it seems :

We need to remove the old 82573L driver, install the updated 82573 network controller driver, create a MS DOS boot pen drive, reboot, flash the card eeprom, and reboot again (there are a lot of subguides to ease the process for newbies USE THEM)

open the terminal ( )

$ sudo rmmod e1000e                       # unload the old driver module

$ sudo rmmod e1000                        # unload the old driver module (errors are OK)

$ sudo rm /lib/modules/2.6.38-8-generic/kernel/drivers/net/e1000e/ -rf                  # remove old drivers (errors are OK)

$ sudo rm /lib/modules/2.6.38-8-generic/kernel/drivers/net/e1000/ -rf                  # remove old drivers (errors are OK)

download and extract to your home directory the latest intel drivers from their site ( )

make sure you have installed build-essential ( )

terminal again and cd to your home directory

$ cd       # to your home directory

$ cd e1000e-1.3.17/src                          #to the extracted drivers directory

$ sudo make install                                 #to install the drivers ( no errors on this side)

now we need to go to the intel site, download and extract the Intel(R) Ethernet Connections Boot Utility, Preboot images, and EFI Drivers ( )        then prepare a MSDOS bootable pen drive and copy the extracted files we just downloaded to the pen drive.

Several ways to create a bootable MSDOS pen drive the Windows way  (PREFERRED) and the Linux1 , Linux2 and Linux3  way (should I use now the saxon genitive, now ? ) choose your favorite one but always  REMEMBER TO PUT THE EXTRACTED FILES TO THE PEN DRIVE.

Now go reading the important NOTE at the end of the page containing the disclaimer !

Now boot using the pendrive ( SUBGUIDE ) and assuming you’re at the command prompt:

c:\>  cd bootutil                        #go to the bootutil directory

c:\>  bootutil -defcfg          #force bootutil to load the default PXE configuration into the controller

# Georgi says ” bootutil -nic=1 -defcfg” it’s better. Try if the other returns an err

after that reboot the pc, and go back to Ubuntu.

Now everything should be working fine.

DISCLAIMER: You probably need to know that the Intel(R) Ethernet Connections Boot Utility WAS NOT designed to be used with on board (also know as OEM) lan cards (is for the PCI cards) therefore there is no sure way to predict it’s interactions with others on board components like USB or SOUND controllers.  I haven’t experienced any problem with my computer and I haven’t seen any negative review using Google (HP dv6000) but there is no way to be 100 %. What I can tell you is that procedure is the only way to make the cards working otherwise you need to buy a new external card.  Eventually use at your own risk and patrol

As usual hope this was helpful to somebody.


Ok, flash post today.

Today at 1:30 AM PST Gmail suddenly stopped working. It seems it is unreachable. Google Apps linked applications are also NOT working.


The Google’s Gmail support team says the following :

We’re aware of a problem with Gmail affecting a number of users. This problem occurred at approximately 1.30AM Pacific Time. We’re working hard to resolve this problem and will post updates as we have them. We apologize for any inconvenience that this has caused.”

Anyway, for all those who are experiencing technical problems accessing Gmail or Gmail is absolutely not working, there is a simple workaround :


What, the hell, is IMAP ?   Just don’t care ! Using gmail with IMAP means : use gmail with Outlook Express, Thunderbird, Mail, Iphone MAIL or any otherIMAP client.

These are some useful links  to configure the main mail clients with GMAIL via IMAP:




Anyway, to configure any client with GMAIL the required settings are the following:

Incoming Mail (IMAP) Server – requires SSL:
Use SSL: Yes
Port: 993
Outgoing Mail (SMTP) Server – requires TLS: (use authentication)
Use Authentication: Yes
Use STARTTLS: Yes (some clients call this SSL)
Port: 465 or 587
Account Name: your full email address (including Google Apps users, please enter
Email Address: your full Gmail email address ( Google Apps users, please enter
Password: your Gmail password

Anyway I’m pretty sure everything is gonna be alright in a couple of hours…


As usual hope this is helpful to somebody.

How To Boot and Run Linux from a USB Pen Drive [Easy Way]


this time I’m gonna show you two easy ways to install and run two common linux distributions from a pen drive using both Windows Xp or Vista or a Linux Distribution, and wizard procedures. It’s like a “Live” distribution, but from a USB drive. The two distributions are Fedora Core 9 (or 8 ) and BackTrack (what is BackTrack ?!? Take a look at this ), both with the persistence feature…what is the “persistence feature” ??? Well, is the possibility to store the changes you’re making to the system (in fact, it’s NOT exactly like a Live distribution)…anyway…

Fedora Core 9 (2 Gb Pen drive is enough, 4 Gb is better )

The Windows’s Way…

1. Insert the pen drive, and make sure it’s empty

2. Download the lastest version of the “liveusb-creator” from here then extract the zip file to a directory and run ” liveusb-creator.exe ”

3. Choose the Fedora Distribution you prefer ( the 9 is really better ! ), choose the USB Drive, then the dimension of the “Persistent Overlay”, the space left to store the modifications to the system, or the files you make. (for 4 gb units, “choose the greatness”…2047 Mb, for 2 Gb… 1024 Mb…less or more… )

4. BUTTON : “Create the Live USB”

5. Wait a couple of hours…

That’s all…now you should have your distribution full working…

The Linux’s Way…

1. Insert the pen drive, mount it and make sure it’s empty

1b. Install YUM if you haven’t got it yet… (your system probably has it already installed…)

2. Open a terminal windows or get a shell, go to an empty directory ( you need a couple of Gb’s free storage space), and give

# yum -y install syslinux PyQt4 git $ git clone git:// 
# cd liveusb-creator 
# ./liveusb-creator

3. Choose the Fedora Distribution you prefer ( the 9 is really better ! ), choose the USB Drive, then the dimension of the “Persistent Overlay”, the space left to store the modifications to the system, or the files you make. (for 4 gb units, “choose the greatness”…2047 Mb, for 2 Gb… 1024 Mb…less or more… )

4. BUTTON : “Create the Live USB”

5. Wait a couple of hours…

That’s all…now you should have your distribution full working…you SHOULD…this is still beta version software…so no one is really sure about that…

Backtrack 3 Final (2 Gb Pen drive is enough, 4 Gb is better )

The Windows’s Way…

1. Insert the pen drive and make sure it’s empty

2. Download the [ USB Version (Extended) ] from the official site

3. Extract the whole .iso file to the USB Drive (feel free to use Winrar )

4. Then open the root folder of the drive (ex. G:\ ), go to “boot” folder

5. Run bootinst.bat and follow the onscreen istructions (just press ENTER if everything is ok )

6. That’s all…. should be working…

The Linux’s Way…

1. Insert the pen drive, mount it and make sure it’s empty

2. Download the [ USB Version (Extended) ] from the official site

3. Extract the whole .iso file to the USB Drive (feel free to use the extractor you prefer…like Ark)

4. Then open the root folder of the drive (ex. /home/media/usb1 or /mnt/sda1 ), go to “boot” folder

5. Run (double click on the icon or “./” to the shell) and follow the onscreen istructions (just press ENTER if everything is ok )

6. That’s all…. should be working…

Hope this was useful…. Happy Holidays…

How-to Install Windows Xp on HP Pavilion dv6236EA


this one is a VERY BRIEF guide about the installation of Microsoft Windows Xp on a HP Pavilion dv6236EA system…

now, first of all you need to DISABLE the “SATA Native Mode” into the BIOS (press F10 at computer boot)…

then you can make a common XP installation…then…this is the *needed* drivers list:

(Ah, the Softpaq packages are the installation programs for the drivers coming from HP)


GeForce Series Video Driver (Softpaq)


Microsoft UAA Driver (Softpaq)


Microsoft KB888111 Hotfix (Original Microsoft Hotfix)


Conexant HD Audio DRIVER (Softpaq – comes with the MODEM driver )


Intel® Chipset Software Installation Utility


Dell Package (Follow the extraction directory, then go into “XP”, this is where the working drivers are located)


Synaptics Touchpad


Lenovo Package (It uses the same interface)


Ricoh 5-1 Card Reader Driver (Softpaq Package)


Webcam 1.3 Mp (Softpaq)


Driver & Application (Softpaq)

After the installation of these drivers, EVERYTHING is working fine for me…

Every device is correctly working…

Hope it was useful…



Q: Why you are not talking about Linux?

A: Because, I dont’want to be stuck in a moment I can’t get out of…


Guide : How-to Install Microsoft Office 2003 in Linux

this time we will talk about the installation and the use of Microsoft Office 2003 in whatever linux distribuction…
It’s a brief and fast guide ! Dont’worry ! 😀
First of all I need to be thankful to the REVIEW by Twickline,  one of the useful, but IMHO uncorrected guides about the installation of Office 2003 under Linux I’ve found surfing; so this lack of “easy knowledge” made me create the guide you’re about to read…but now…stop talking around…let’s start ! 😀

First, what will work using this procedure:

Word 2003
Excel 2003
Power Point 2003
Publisher 2003

Than what will NOT work
Access 2003 (IMHO anyway it’s USELESS)
Infopath 2003
Outlook 2003 (Useless this one too. 🙂

So let’s start:

Download, or install Wine 0.9.37 DO NOT install the lastest version of Wine, because is NOT working…

So DO NOT use your packet manager, (Apt, Synaptics)…but download this “old” version…
For Example at this link you can find the .deb (Ubuntu & Debian Packages) files.

Go to your home folder (aka /home/sorcerer01) then go to .wine/drive_c/windows/system32
EX : “cd /home/sorcerer01/.wine/drive_c/windows/system32”

Rename richedit32.dll and richedit20.dll to richedit32.bak and richedit20.bak
EX:“mv richedit32.dll richedit32.bak” & “mv richedit20.dll richedit20.bak”

Make richedit*.dll “native”
EX: give “winecfg” to bash, go to “Libraries”, insert the dll names, into the mask

Download the richedit30 update to desktop
Download Link

Install richedit
EX: “wine richedit30.exe”

Download the XML Parser
Download Link (only msxml3.msi)

Install the XML parser using wine
EX: “msiexec /i msxml.msi”

Follow the on-screen instructions

Set “msxml3”, “msxml3” and “msxml3.exe” to native
EX: use “winecfg” as before described

Add Owner and Organizaion Informations to Wine
EX: give “regedit” to bash,
      go to [HKLM\Software\Microsoft\Windows\Current Version]       
      add your name to the keys “RegistredOwner” and “RegistredOrganization”
      then go to [HKLM\Software\Microsoft\Windows NT\Current Version] and
      and proceed as before


Mount the Office 2003 CD with the option to see the hidden files…

EX “Insert the cd-rom into the drive”
      “Make sure it is not auto-mounted (umount /dev/cdrom as root)”
      “give this or something similar to bash (it depends on your distribution…you probably should know the right                                                                       command if are reading this guide)
       “mount -t iso9660 -o unhide /dev/cdrom /media/cdrom”

Start the installation procedure
EX: go to the cdrom directory and give
          “wine setup.exe”

Follow the onscreen procedure to install Microsoft Office 2003

Try to start an application
EX: ” Probably you got into a new main menù voice called “Wine” where you can find the Office programs, anyway the bash command is…
       “wine “/home/sorcerer01/.wine/drive_c/Program Files/Microsoft Office/OFFICE11/winword.exe” “

       and so on…

FGA (Frequently Given Answers)

YES, you really need that old version of wine. (newer version are not working…at least up to 0.9.48)

Yes, you have to change “sorcerer01” to your home directory name…(usually it’s you user name)

Yes, if you’re using Ubuntu the installation works with the “sudo” command…

You shouldn’t need be root for make wine running and – or – install MS Office…

You just need to be root to install wine and maybe to mount the cdrom…

I am not sure, I’ve heard of people activating Office 2003 in linux…probably you should know what to do about the problem….

No, Wine-doors CAN make it working…but only if you’ve installed Wine 0.9.37

No, Wine programs, are NOT shared between different users

No, If you are using Beryl or Compiz, you probably DON’T NEED to disable them.

No, I don’t know how to run Access 2003

No, at this time I don’t how to make Office 2007 running

FAQ (Frequently Asked Questions)

Q: Why to install 0.9.37 and now the lastest one ?

A: The problem is a common error, probably related with the implementation of the msi.dll into the newer and older versions od Wine; this error makes EVERY Office Application to hang up with this error code

“Microsoft Office Word has not been installed for the current user. Please run setup to install the application”

more informations about the bug are here , here , here, and here.
The only, current, solution is to downgrade to 0.9.37

Q: I’ve already got a newer wine installation, what to do ?

A: Well…It depends…simply try to remove the program…and install the old one…(all your files wil be kept), If everything is working anyway…you’re okay… !
If your applications aren’t working anymore you probably need to keep two different installations of wine..but I think this is really OT…

As usual, hope this was helpful…to someone…

YAHT, Yet Another How-To Install webcam on Pavilion dv6000 & dv9000 series


just installed the new Ubuntu 7.04 “Feisty Fawn” on my laptop (HP DV6236EA), everything worked fine…except for the installed webcam…

UPDATE: after installing Gutsy Gibbon….everything worked fine…except for the installed webcam

so…after…a LONG (10 minuts) hard searching session…I’ve created this how-to…hope it’s useful…

HOW-TO Install Ricoh webcam 05ca:1810 and others to Ubuntu 7.04 and, probably, other, Debian based, Linux distribution; this webcam is a part of HP dv6000, dv9000 an Sony…

First of all, make sure You got a Ricoh Webcam so from a terminal give:

sudo lsusb

the output should have a line like this

Bus 005 Device 002: ID 05ca:1810 Ricoh Co., Ltd

Different ricoh webcam’s ID (05ca:1810) requires different drivers,
but the driver for 05ca:1834 is mostly compatible; in fact you can use this how-to and this drivers for these ID:

05ca:1830 Sony Vaio SZ (Sony Visual Communication Camera VGP-VCC2 )
05ca:1832 Sony Vaio UX (Sony Visual Communication Camera VGP-VCC3)
05ca:1833 – Sony VAIO AR webcam (“Sony Visual Communication Camera VGP-VCC2)05ca:1834 – Sony VAIO AR webcam (Sony Visual Communication Camera VGP-VCC2)
05ca:1835 – Sony VAIO SZ webcam (Sony Visual Communication Camera VGP-VCC5)

05ca:1836 – Sony VAIO FE and AR (Sony Visual Communication Camera VGP-VCC4)

05ca:1870 – HP Pavilion built-in webcam
05ca:1810 – HP Pavilion built-in webcam


so to install the drivers follow this two step guide :

IF USING 7.04 Feisty Fawn 

follow this link [EXPIRED ricoh-webcam-r5u870-2.6.20-16-generic_0.10.0-4_i386.deb] to download the first .deb package, open & install It using your package manager (in Ubuntu is

IF USING 7.10 Gutsy Gibbon

follow this link [EXPIRED ricoh-webcam-r5u870-2.6.22-14-generic_0.10.0-4_i386.deb] to download the first .deb package, open & install It using your package manager (in Ubuntu is

Then, for Both

follow this link [EXPIRED ricoh-webcam-r5u870_0.10.0-4_i386.deb] to download the second .deb package, open & install it using your package manager.

If everything is okay, your wecam is Up & Running…maybe you can try it using Gaim…

The original post where drivers were presented is :

Many issues report problems with the Kopete application…it’s a Kopete problem…


Playing Manowar – Carry on