So instead of adding a rule to disable telnet, you will prefer to clone the rule set and modify it.

#ipfilter –clone CurrentSec -from default_ipv4
#ipfilter –show (write down the rule number for Telnet 23)
#ipfilter –delrule CurrentSec -rule 2
#ipfilter –addrule CurrentSec -rule 2 -sip any -dp 23 -proto tcp -act deny
#ipfilter –save CurrentSec
#ipfilter –activate CurrentSec

First off, there a few commands and output that will give you a good starting point.

C:\Windows\system32>cscript slmgr.vbs /dlv
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Software licensing service version: 6.1.7600.16385

Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System – Windows Server(R), RETAIL channel
Activation ID: 039998e3-3ef5-4adf-b758-mnbvczxlkjjhh
Application ID: 55c92734-d682-4d71-983e-lkdaskdjaskl
Extended PID: 00477-4444-444-000000-00-1033-7600.0000-3482009
Installation ID: 006386735361234567898785803475982043689521915735258065
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: 2YYCD
License Status: Initial grace period
Time remaining: 43200 minute(s) (30 day(s))
Remaining Windows rearm count: 2
Trusted time: 4/27/2010 11:09:12 AM

Or its equivalent with less information slmgr /dli.

In that case, it seems that KMS client is not even set here.

First off, you may want to tell the server where to look to get Keys using the following commands.

To know which server should be register you may want to check the DNS record that

C:\Windows\system32>nslookup -type=srv _vlmcs._tcp.xxxx.net
Server:  rrrpdcad02.xxxx.net
Address:  10.9999.15

_vlmcs._tcp.xxxx.net   SRV service location:
priority       = 0
weight         = 0
port           = 8081
svr hostname   = rrrmskms01.xxxx.net
rrrpmskms01.xxxx.net   internet address = 10.99.98.97

With this information you can now register for this server.

C:\Windows\system32>cscript slmgr.vbs /skms rrrpmskms01:1688
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Key Management Service machine name set to rrrmskms01:1688 successfully.

You will then need to enter a valid key if not already done with you unattended install. Please check the below table with MS provided keys for activation using KMS.

C:\Windows\system32>cscript slmgr.vbs -ipk YC6KT-GKW9T-YTKYR-T4X34-R7VHC
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Installed product key YC6KT-GKW9T-YTKYR-T4X34-R7VHC successfully.

then trying the activation using the command below I would get another error.

C:\Windows\system32>cscript slmgr.vbs /ato
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Activating Windows Server(R), ServerStandard edition (039998e3-3ef5-ddasdasdass8-d25fa0128ff4) …
On a computer running Microsoft Windows non-core edition, run ‘slui.exe 0x2a 0x80072EE2′ to display the error text.
Error: 0x80072EE2

Using the mentioned command I would find that 0x80072EE2 means that the operation timed out. Very well, then I may facing some communication errors.

Indeed, as you may have noticed I made a mistake above not using the right port. I used 1688 which the default port instead.

You can also check on your KMS for a status using the slmgr /dlv command:

Key Management Service is enabled on this machine
Current count: 50
Listening on Port: 8081
DNS publishing enabled
KMS priority: Normal

Be sure to use the port that is given by the volume license DNS entry and make sure it communicates. As you may have guessed there are 2 ways a new server where a KMS is install will register. Of course after changing to the right port and can try -ato (activation) again.

1. by using the DNS to automatically locate the KMS
2. or just register it manually using the commands above

When rightfully registered the /dli or /dlv will give you something like that:

C:\Windows\system32>cscript slmgr.vbs -dli
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.

Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System – Windows Server(R), VOLUME_KMSCLIENT channel
Partial Product Key: R99HC
License Status: Licensed
Volume activation expiration: 259200 minute(s) (180 day(s))

Key Management Service client information
Client Machine ID (CMID): 70e4de42-rewa-4c93-gf45-a6d372bc0a19
Registered KMS machine name: rrrpmskms01.xxxx.net:8081
KMS machine extended PID: 55041-009999-313-09999-03-1033-6002.0000-3442009
Activation interval: 120 minutes
Renewal interval: 10080 minutes
KMS host caching is enabled

Activation Keys table (taken from here)

The sysadmin who gets to:

Wear the beeper 24 x 7? The sysadmin.

Have almost every thought interrupted? The sysadmin.

Mind the gap between hype and reality? The sysadmin.

Watch over the “minor details”? The sysadmin

Listen to hold music while a blowtorch singes the body part that gets copied? The sysadmin

Have purchase recommendations be ignored political decree? The sysadmin.

Face the wrath when somebody else’s bad idea breaks? The sysadmin.

Stay at work while the bosses go out for a round of mucky muck? The sysadmin.

Have everybody else tell them what they really ought to be doing? The sysadmin.

First I could not get into that VM remotely as it appeared as offline. This said, VI showed the VM as healthy and online.

Trying to get to it using the Console from VI showed the following error:

As you can see I was afraid that some of the SAN path were down or some kind of painful problem with the SAN. No, no a quick ssh in showed that the mentioned volumes were online, accessible and all SAN paths were up.

So I do power off and restart the VM: no success. Restart the ESX (after vmotioning all VMs): no success.

Eventually I find that in the settings of the VM, there was  a reference of some floppy image pointing to a volume (not even on the same volume). I changed that option to Client Device and voila everything was back to normal.

Looking that information up on the VMware KB or community forum  doesn’t provide any solution.

Enabling HA gave the error:
“Cannot complete the configuration of HA agent on the host. See the task for details for addional information. ”

Without much details I was almost ready to blame it on ESX4i. However after checking everything I found out that my DNS servers settings were wrong.

Changing my DNS to the right IPs and HA configuration worked like a charm.

Obviously my sticky keys did not help but of course stressed out the reminder that HA relies on DNS heavily.

In an attempt to understand, I was able to find the signification for one of them. I hope I find more.

“299″ Line Mechanic call. There are “Line Mechanic’s” posted at Kipling, Keele, St.George, Bloor, Chester, Kennedy, Eglinton, St.Clair West & Sheppard.
“101 – 120″  Supervisors
“122″  Subway Line Supervisor
“199″ Subway Line Mechanic Supervisor
“143″ Chief Supervisor
“147″  Fare Supervisor
“148″ Transit Patrol Security
“201 – 220″ TTC Armored Trucks
“301-310″  Streetcar Track/Overhead Maintenance
“506″ Station Janitor

For this recipe, you will need:

• adrestore, a great tool from our friend Mark
• Admin rights on AD, to perform what you have to do

For your sake, AD keeps deleted record for 30 days by default. If it was an important account, there are great chances you notice it is missing before the 30 days. Past those 30 days, you will need to use the “standard authoritative” AD backup method.

Your application using the deleted account will complain and a query on AD reveals it is not there. Not a problem, just follow the 4 easy steps below:

1. Restore the missing account
adrestore.exe -r MissingAccount
Enumerating domain deleted objects:
cn: MissingAccount
DEL:eab4d5e6-493b-4a64-aae8-360e730a5938
distinguishedName: CN=MissingAccount\0ADEL:eab4d5e6-493b-4a64-aae8-360e730a5938,CN=Deleted Objects,DC=rgare,DC=net
lastKnownParent: OU=Service Accounts,OU=Users,OU=Montreal (MTL),DC=COMPANY,DC=net

Do you want to restore this object (y/n)? y

Restore succeeded.

Found 1 item matching search criteria.

2. Query to check its existence
dsquery user -name MissingAccount
“CN=MissingAccount,OU=Service Accounts,OU=Users,OU=Montreal (MTL),DC=COMPANY,DC=net”

3. Reset Password as restored account comes back empty
net user /domain MissingAccount Password

4. Activate Account
dsquery user -name MissingAccount| dsmod user -disabled no
dsmod succeeded:CN=MissingAccount,OU=Service Accounts,OU=Users,OU=Montreal (MTL),DC=COMPANY,DC=net

At this point and under 3 minutes, the deleted account is restored and ready to be used. It even kept its SID but you will have to repopulate some of its attributes such as Description and so on.

I think it is easier to understand if you look back in the past and see how those were used.

RM systems were first developed to manage paper files. They could also manage other physical records, such as microfilm and photographs. RM systems help you perform the
following tasks:
• Opening, closing and registering files, folders, dockets, and individual documents.
• Tracking the location of files.
• Charging files out to users.
• Classifying records.
• Indexing records.
• Searching for records using keywords and other search criteria.
• Managing the active and semi-active retention of the records.
• Managing the disposal of records.
• Managing access to and security of records.
Newer versions of RM systems can capture and manage finished electronic records.
They streamline many of the most time-consuming records management tasks. Using an RM system makes it easier to search for records, transfer them to the records centre, and dispose of them.

RM systems were created to make it easier to manage paper records. In contrast, DM systems were created to make it easier to use electronic records. DM systems are designed to keep track of changes to electronic records, share them, and route them to different people.
DM systems integrate with most software packages that you use to create electronic records.
Typically, when you try to send an e-mail message or save an electronic record, the DM system will prompt you to fill out a profile form. The electronic record is saved into the DM system and stored on a DM server. You must go through the DM system to retrieve the record.
DM systems have several strengths, including:
• Capturing electronic records at the point of creation.
• Full text searching of documents.
• Tracking of different versions of the same document.
• Monitoring who has viewed a document.
• Capturing document images from a scanner.
• Passing documents along a workflow. This is useful where a document must be passed
through several people for editing, response, review, or approval.
Early DM systems did not manage records. They had limited ability to classify records and they could not apply retention and disposition schedules.

To Sum Everything Up
Records Management:
• Management of the record is more important than the content of the record
• The record never changes (although its properties might)
• Records require access controls, lots of them

Document Management/Collaboration:
• Without content there is no document
• The document changes a lot, that’s the whole point of collaboration
• Access controls restrict and impede collaboration, the fewer there are the better

I liked ING Direct because of their high interest rate, not that high, but usually the higher of all, especially against Canadian banks.

Saving Account at 1.2%

ING Direct is an online bank like PC Financial that only offers saving account (not only, but there is no checking account). To and from where you can transfer money at no fee.

It is very easy to use and their “Goal Set” tools are really made for what it is for.

I have just set 2 saving accounts. One for Vacation saving and the other one to build my emergency fund. Using the Goal tool, I can just initiate my custom Automated Saving Program so that some money is put aside automatically. This can also be done manually between the banks you link ING Direct with.

TFSA at 3%

What really led me towards ING direct is their 3% TFSA rate. I had been looking for “conservative” place to shelter some money but never found anything interest as interest were very low. At least my first “conservative” TFSA sheltering is earning a bit.

Get $25 for opening an account

All they needed was basic personal info along with basic banking info from which the client will be transferring money from.  After that, a personal cheque needs to be mailed in to verify banking information.  From the beginning to end, the whole process took about 3 business days, with about 20 minutes worth of “work”.

You can use $25 using their referral program.

1. Apply for a new account
2. When asked, use the orange key code 33784873S1
3. Deposit at least $100
4. Get $25

After your account is opened, you will see a free $25 in your ISA account (or new ISA if you did not have one).

Very pleased

So far I am very impressed and pleased by the ease of use and competitive interest rates. I think ING Direct does a good job for your saving accounts!

How do you use your ING Direct account? Have you tried their other products?

In general insurance is only worth it when it covers events that are very unlikely and which, if they happened, they would pretty much ruin your life or the life of someone you care about. For example, life insurance if you have dependents, fire protection insurance, disability insurance. Those all protect you against things that are unlikely to happen but if they happen and you don’t have insurance, someone’s life gets ruined.

Insurance does not make sense for things that are cheap, or events that are likely. You shouldn’t insure a television (aka buy an extended warranty). Balance protection insurance most likely lies under this category.

To understand why I say this, let’s review how the insurance company makes money. Imagine a world where every house costs $100K and the chance of a house fire is 0.1%. Thus, the “expected cost” is $100K x 0.1% = $100. That’s not very much. The problem is the risk. If your house does burn, you lose your life’s savings. So the insurance company comes along and offers to insure your house if you pay them $120. The company does this for 1,000 houses. One of those houses does burn, so the insurance company received $120,000 and paid out $100,000 for the one house that did burn. The other $20,000 is profit.

The point of the example is that the insurance company will always charge you more than the “expected cost” of the event. You are guaranteed to lose money “in average”. In this sense, you are always “over-paying”. For events that are unlikely and would significantly hurt your life, this extra cost is worth it. For things that either happen very often or are low cost, insurance isn’t worth it.

Let me give you an example of the latter: Suppose that you know with 100% certainty that you are going to lose $100. This is a high-probability event. Would you pay $120 to be insured against the certain loss of $100? Of course not.

Were do you draw the line?

Well, that’s a personal choice. It depends on how risky something is for you and your tolerance for risk. But the basic principle is intact. Decide how you want to define “unlikely” and “significant cost” and make sure you only pay insurance for things that are unlikely and would incur a significant cost.

You may want to check this link for more statistical information:

http://www.cbc.ca/marketplace/blog/credit_balance_insurance.html