Is is it correct that I no longer need a tftp server to download/install IOS upgrades, phone firmware, and /or licenses? I am confused about the need for the archive command I see referenced. Can I just use a USB flash, download thefiles from cisco, copy to a USB flash and inert into the usb port on the 2911? Is there anything I need to know with regard to PAK files or any file format that needs special procvessing to complete my objective? Any gottchas to be aware of?
You can boot or store firware files and IOS images on a USB drive and use but you will need a Cisco USB flash memory. Any USB key wont work afaik and havent tried it yet. You will have to set the path accordingly.
so if I cant use any USB flash and dont have a cisco flash, do I have to rely on a windows based tftp server to download the files from CCO then copy from them from this tftp from the router? Is there any better method / option?
You could use TFTP or FTP servers. TFTPD32 is a light weight and free TFTP server. TFTP is only needed to upload the files to the router, downloading from CCO is like any other browser download. IMO, TFTP/FTP is the fastest and easiest, maybe others have a different opinion.
What Im confused about is the config files for teh phone and the firmware. As I undersand it- the firmware for the phone gets first loaded / stored on the cme tftp server so it can be downloaded to phone (dhcp option 150). The config file for the phone is created when you enter #create-cfg - but really what does that do and how can I verify its ont eh cme tftp server to be downloaded by the phone?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.