Do you miss Scribble (an origami-esque cat) or Power Pup (a superhero dog)

I receive a strange request today from a customer.

She missed the office assistant 2007 Power Pup (a superhero dog)- She is now using office 2003 and she is ready to go back to 2007 just for SUPERHERO DOG.

I can't believe people will miss that thingy. As a tech, I wanted microsoft to remove that annoying thing. From Today, I know I was wrong and SELFISH. People love and missed their little dog or cat.

So, here what I did to answer to the need of my customer and STOP being selfish.
TECH are not always right.

clic

1- start, setting, control panel
2- Add or Remove program
3- microsoft office and CLIC ON CHANGE (do not clic on REMOVE)
4- add or remove features
5- next
6- check mark the box - "choose advanced customization of applications".
7- expand Office Shared Features
8- expand office Assistant
9- choose THE OFFICE ASSISTANT THINGY that you love ex. ROCKY, OR CLIPPIT
10- Choose run from my computer

11- clic updte

and you are done.

cisco switch - display only connected interface

if you type, sh int status, you will get the status of all interface. But what about if I want just to display the interface with status connected?
I am using the following command until I find a better solution is:
sh int status | e not (display all interfaces excluded those with status NOTCONNECT).


SWITCH_B#sh int status

Port Name Status Vlan Duplex Speed Type
Fa0/1 IP PHONE 1 connected 50 a-full a-100 10/100BaseTX
Fa0/2 IP PHONE 2 connected 50 a-full a-100 10/100BaseTX
Fa0/3 IP PHONE 3 notconnect 50 auto auto 10/100BaseTX
Fa0/4 notconnect 50 auto auto 10/100BaseTX
Fa0/5 connected 50 a-full a-100 10/100BaseTX
Fa0/6 notconnect 50 auto auto 10/100BaseTX
Fa0/7 connected 50 a-full a-100 10/100BaseTX
Fa0/8 notconnect 50 auto auto 10/100BaseTX
Fa0/9 notconnect 50 auto auto 10/100BaseTX
Fa0/10 notconnect 50 auto auto 10/100BaseTX
Fa0/11 notconnect 50 auto auto 10/100BaseTX
Fa0/12 notconnect 50 auto auto 10/100BaseTX
Fa0/13 notconnect 1 auto auto 10/100BaseTX
Fa0/14 notconnect 1 auto auto 10/100BaseTX
Fa0/15 notconnect 1 auto auto 10/100BaseTX
Fa0/16 notconnect 1 auto auto 10/100BaseTX
Fa0/17 notconnect 1 auto auto 10/100BaseTX
Fa0/18 notconnect 1 auto auto 10/100BaseTX
Fa0/19 notconnect 1 auto auto 10/100BaseTX
Fa0/20 notconnect 1 auto auto 10/100BaseTX


SWITCH_B#sh int status | e not

Port Name Status Vlan Duplex Speed Type
Fa0/1 IP PHONE 1 connected 50 a-full a-100 10/100BaseTX
Fa0/2 IP PHONE 2 connected 50 a-full a-100 10/100BaseTX
Fa0/5 connected 50 a-full a-100 10/100BaseTX
Fa0/7 connected 50 a-full a-100 10/100BaseTX
Fa0/24 CONNECT TO SWITCH connected trunk a-full a-100 10/100BaseTX

OFFICE 2003 NETWORK INSTALLATION

Running Setup to create an administrative image
To distribute Office from a network server, you must first install Office on an administrative installation point by running Setup.exe with the /a command-line option. Then you can customize your Office configuration before running Setup on users' computers.

To create an administrative installation point for Office

Create a share on a network server for the administrative installation point.
The network share must have at least 550 megabytes (MB) of available hard disk space.

On a computer that has write access to the share, connect to the server share.
The computer must be running a supported operating system: Microsoft Windows® 2000 Service Pack 3 or Windows XP or later.

On the Start menu, click Run, and then click Browse.
On the Office 2003 CD, double-click setup.exe and add /a to the command line.
Note that if you are using the Office 2003 Select CD, type the name of the Setup program for the package you are installing. For example, if you are installing Office 2003 Professional from the Select CD, type SetupPro.exe /a on the command line.

Enter the organization name that you want to define for all users who install Office from this administrative installation point.
Enter the server and share you created as the installation location.
Enter the 25-character Volume License Key and click Next.
You must enter a valid Volume License Key when you create the administrative installation point; users who install Office 2003 from this administrative image do not need to enter the product key when they install Office 2003 or start an Office 2003 application for the first time.

Accept the end-user license agreement and click Install.
By accepting the agreement here, you are accepting on behalf of all users who install Office from this administrative installation point.
Setup copies the files from the Office 2003 CD to the administrative installation point, extracts the compressed cabinet (CAB) files, and creates a hierarchy of folders in the root folder of the share.


--------------------------------------------------------------------------------

Note When you install Office 2003 and you set features to run from the network (Run from Network or Run All from Network), you must create your administrative installation point in a subfolder on the share; for example, \\server\share\admin_install_point\setup.exe. If Setup.exe is stored at the root of the share, Office 2003 features do not run properly.


--------------------------------------------------------------------------------

The following table identifies the location of key files on the Office 2003 administrative image.

File Location
Setup.exe Root of the administrative image
Setup.ini Files\Setup
Office 2003 package (MSI file) Root of the administrative image
OPC files used to clean up previous versions Files\Program Files\MSOffice\Office11


Setup also modifies the Windows Installer package for Office, identifying it as an administrative installation package and setting the ProductID and COMPANYNAME properties accordingly. After you create the administrative installation point, you make the share available to users by providing them with read access.

When users run Setup to install Office, any Office features that are installed to run from the network use this administrative installation point as the source of Office files, and Office runs the features over the network from this server. Similarly, for features that are set to be installed on first use, Office copies files from this server when needed. If you install features in one of these two states, then you must keep this network server available to users. You can copy the administrative image to one or more backup servers to help ensure that users always have access to the source.

When users install Office from the administrative installation point, Setup uses the organization name that you specify as the default. With the Office 2003 Custom Installation Wizard, you can create a Windows Installer transform (MST file) that modifies the organization name during installation. This flexibility allows you to create different organization names for different groups of users in your organization.

You can specify the organization name on the Setup Properties in the Office Resource Kit Reference.


--------------------------------------------------------------------------------

Toolbox The Office 2003 Editions Resource Kit (ork.exe) includes the Custom Installation Wizard as part of the core tool set and is available as a download. You can find this downloadable file on the Office 2003 Resource Kit Downloads page.

Create a Hunt-group

Router(config)# voice hunt-group 1 longest-idle

Router(config-voice-hunt-group)# pilot 7501

Router(config-voice-hunt-group)# list 7001, 7002, 7023, 7028, 7045, 7062, 7067, 7072, 7079 Router(config-voice-hunt-group)# final 8000

Router(config-voice-hunt-group)# hops 6

Router(config-voice-hunt-group)# timeout 20

Router(config-voice-hunt-group)# exit

FREE CCNA VOICE LAB - HOME LAB - ip phone 7911 can't upgrade

My lab is available to anyone who want to practice. Plz just email me.

My lab has changed - It looks exactement like the one in JEREMY CIORAS "The official CCNA VOICE" book.

1 - Cisco 2801 with 1GB of usbflash -- CME and TFTP Server
1- CISCO 2611XM configured as the DHCP
1- CISCO switch 2950 - -- SWA-- where the CME and the DHCP are connected
1- CISCO switch 3550 ---- SWB --- where the ip phones are connected
3 - ip phones - (7941G, 7940G,7911)
1- PC pour FTP server and CIPC


So, I decided to write erase all the configurations and rebuild the lab.

After setting up the tftp server, and loads the appropriate firmwares, the cisco 7911 couldn't upgrade the firmware.

I reboot the phone several time, configure to factory default, but still nothing.

So, I decided to compare line by line the tftp-server command and the the
ME#dir flash:/phone/7906-7911
Directory of flash:/phone/7906-7911/

63 -rw- 2496963 Feb 10 2009 12:12:44 -08:00 apps11.8-3-2-27.sbn
64 -rw- 551014 Feb 10 2009 12:12:48 -08:00 cnu11.8-3-2-27.sbn
65 -rw- 2387207 Feb 10 2009 12:12:58 -08:00 cvm11sccp.8-3-2-27.sbn
66 -rw- 326315 Feb 10 2009 12:13:00 -08:00 dsp11.8-3-2-27.sbn
67 -rw- 307192 Feb 10 2009 12:13:02 -08:00 jar11sccp.8-3-2-27.sbn
68 -rw- 658 Feb 10 2009 12:13:02 -08:00 SCCP11.8-3-3S.loads
69 -rw- 662 Feb 10 2009 12:13:04 -08:00 term06.default.loads
70 -rw- 662 Feb 10 2009 12:13:04 -08:00 term11.default.loads

and


CME#sh run | s i tftp-server flash:/phone/7906-7911
tftp-server flash:/phone/7906-7911/apps11.8-3-2-27.sbn alias apps11.8-3-2-27.sbn
tftp-server flash:/phone/7906-7911/cnu11.8-3-2-27.sbn alias cnu11.8-3-2-27.sbn
tftp-server flash:/phone/7906-7911/cvm11sccp.8-3-2-27.sbn alias cvm11sccp.8-3-2-27.sbn
tftp-server flash:/phone/7906-7911/dsp11.8-3-2-27.sbn alias dsp11.8-3-2-27.sbn
tftp-server flash:/phone/7906-7911/SCCP11.8-3-3S.loads alias SCCP11.8-3-3S.loads
tftp-server flash:/phone/7906-7911/term06.default.loads alias term06.default.loads
tftp-server flash:/phone/7906-7911/term11.default.loads alias term11.default.loads


Then I found out that a line was missing

tftp-server flash:/phone/7906-7911/jar11sccp.8-3-2-27.sbn alias jar11sccp.8-3-2-27.sbn


Yes that single line can messup the old phone.

so, please be carefull.

Again, if you want to have access to my home lab and practice, feel free to contact me.

The messaging interface has returned an unknown error...." OUTLOOK 2003 - Shared folder

I received a phone call from a customer today about outlook 2003 returning the following messsage when she try to print a shared calendar. "The messaging interface has returned an unknown error. If the problem persits, restart Outlook." She is able to print her own calendar without any problem.

Here how I fixed it.

1- double-clic the shared calendar

2- File, print, and clic define styles

3- Edit, and uncheck Taskpad

4- clic ok, ok And voila - she is back in business

SanDisk Ultra II Flash memory card on cisco 2801

I am happy today that my cisco 2801 is working again.

Yesterday, I had a power outage and my cisco 2801 went crazy. It booted only on rommonitor mode. I restarted it couple time and still the same.

I tried to xmodem a new IOS to the flash but without success and so I decided to ymodem.

The Ymodem worked, the ios was now in my DRAM but I figured out fast that the cisco compact flash was gone. I couldn't format it.

So, I decided to use a different cisco compact flash drive (64mb). The new flash worked fine and I was able to boot in normal mode.

I was happy but the battle wasn't over. I am using this cisco 2801 as my CME for my CCNA VOICE LAB. So, 64mb of compact flash wasn't enough.

Here is the good part. I decided to try the SANDISK ULTRA II flash card.

I went at officemax and find one, a 1GB for only $19.99 - I decided also to buy a 5in1 card reader.

steps:
1- plug the card reader in my pc and insert the sandisk ultra II compact flash in the reader

2- format the card using FAT16 (ATTENTION : You MUST format this card as FAT16)

3- copy my ios file from my pc to the flash card (I am still in my pc - just drag and drop)- The IOS I use is : c2801-adventerprisek9-mz.124-20.bin

4- format a usb flash drive (FAT16)- It is a 1gb usb flash drive- and copy the cme-full-4.3.0.0. tar and the IOS c2801-adventerprisek9-mz.124-20.bin
THIS STEP is not required - but it make things easier.

5- Power down the cisco 2801 and insert the usb flash drive and the SANDISK ULTRA II flash memory card.

6- Power on the cisco 2801, the boot process will take longuer than usual - just be patient.

7- You are now back in business, your cisco router should boot now normally.

8- Because I am using my cisco 2801 as my cme, I tranfered all my cme to the flash.

from the router prompt (in priv mode), type

Router# archive tar /xtract usbflash0:/cme-full-4.3.0.tar flash

As you noticed, I xtract my file from USB flash drive (that is why I have step 4)- The transfer is way much faster than using the tftp server.

and VOILA, everything work like a charm. I save hundred of box -

So, why cisco compact flash so expensive?

Important : IT DOESN'T WORK WITH A 2GB COMPACT FLASH.