Upgrade to 4.2 WCS

Has anyone taken the leap yet?
I was going to my WCS today and then do my controllers tomorrow afternoon.
I was going to take Cisco on its' word:
Upgrading to a New Software Release
The Cisco WCS release must be the same or more recent than the controller software release. Upgrade the Cisco WCS first to prevent any unexpected problems. Cisco WCS supports database upgrades only from the following official Cisco WCS releases:
from http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCSRN4_2.html#wp44431
but figured I would ask first.

There are other "unresolved caveats" in 4.2 (a list that is growing significantly faster and larger than the "resolved caveats" list):
WLC 4.2.61 Release notes: http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn4200.html
WCS 4.2.62 Release Notes http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCSRN4_2.html
Specifically, the following was of concern to me:
CSCsk16314-Access points start downloading new software before the controller has been rebooted.
Workaround: None.
Since the LWAPs immediately begin downloading code prior to the WLC's reboot as the final stage of its upgrade.
This results in the possible interruption of up to 10 LWAPs in mid-upgrade. According to Cisco, you really do not want to interrupt the LWAP in the middle of an upgrade. If you do, you may have to reload the APs from scratch which could take some time... if you can still communicate with them. If not, you may have to get physical access to them.
If you have multiple controllers, then the potential problem can be quite significant.
It would seem to make sense to isolate the controllers from the LWAPs during the upgrade to the controller(s) and, once the controllers upgrade and reboot, then re-establish connection to the access points.
On the flip side, I had a customer decide to "go for it" on his 300-LWAPP, multi-controller system and he ran the gauntlet successfully without isolating the LWAPs... but as they say, Caveat Emptor (which means, when loosely translated, "we have been sold a bunch of caveats").
- John

Similar Messages

  • How to upgrade the OS on WCS(Linux)?

    I want to upgrade my WCS to RedHat Linux 5.0.  I have burned the iso image to a cd, rebooted the WCS and find nothing happening.  Prior to rebooting, I start a SSH connection to the appliance so I figured that I would see it come up and the upgrade start but then I lose the connection.  Does anyone have any info on upgrading the OS on a WCS?  TIA

    Thanks for the reply.  I simply copied the iso to a cd.  during the reboot, I lose my console connection.  So it sounds like I am not burning the cd correctly?

  • Any experience of upgrading a WLSE to WCS?

    Hi All,
    Has anyone out there upgraded a WLSE appliance to WCS? It seems a fairly easy process going by the instructions on the site but I wonder if there are any pitfalls to be wary of?
    Any advise would be appreciated.
    Thanks
    Scott

    It's works very well !
    Normally you will not found any problem.
    I do that 3 weeks ago, and works fine.
    Be sure to have the 2 CDs with you to do the process. And you should be physically connected to the console port.
    The process can't be done remotly.
    The migration guide is on:
    http://www.cisco.com/en/US/products/ps6305/products_configuration_guide_chapter09186a00806b71db.html
    Regards,
    Emilio

  • Upgrade recommendations for controllers / WCS

    Currently running Wism on 4.2.61 and have another to put MESH code on. Our WCS release is 4.2.62.0
    Would appreciate input on the right mix of releases to move to supporting mesh on one wism and no mesh ap's on the other - for now. thx

    The latest mesh release is 4.1.192.35M MESH
    and the latest non-mesh is 4.2.176.0
    There are the 5.X releases but I keep hearing people say not to go to it. They also just released 5.2.157.0 which supposedly supports mesh again. However, in 5.X you can't use 1505 and 1510 Mesh APs nor can you use the 1000 Series Access Points (like the 1020).
    With all the said, I'm guessing your safest bet is to do one controller on 4.1.192.35 and the other on 4.2.176.0...
    What kind of mesh are you looking to do anyhow? Enterprise Wireless Mesh (indoor)? or just the 15XX series outdoor mesh APs?

  • Upgrading to NCS from WCS. Can i import my maps APs etc into NCS?

    We've bought NCS and are currently running WCS 7.
    I want to know is it possible to import in all the Maps and the APs that I've already in place in WCS or do i have to start from scratch??
    Any feedback appreicated.
    Thanks

    you can migrate your data.
    http://www.cisco.com/en/US/docs/wireless/ncs/1.0/release/notes/NCS_RN1.0.0.html#wp83675
    Steve

  • WCS upgrade to Prime 1.2

    I'm currently running WCS 7.0.230 ready for upgrade to Prime 1.2. Reading Cisco docs, the path is to upgrade from WCS to NCS 1.1.1.24 firstly, then to Prime 1.2
    so far...
    export.bat all > wcs-export.zip
    also performed a backup via the GUI backup tool
    have a NCS 1.1.1.24 - 30 day eval license (docs say eval is enough before upgrading to Prime 1.2 which you have purchased)
    A couple of things are not clear to me,
    http://www.cisco.com/en/US/docs/net_mgmt/prime/infrastructure/1.2/quickstart/guide/cpi_qsg.html#wp56675
    currently WCS runs
    7.0.230
    Feature - plus
    AP limit 150
    Type permanent
    Does this mean I need to uninstall WCS to install NCS cleanly or is there an upgrade path without uninstalling WCS manually? In the download section you can only download  for Small/medium/Large. I intend to download medium, but again there are no specifics I can find in relation to my WCS license i.e. - AP limit = NCS medium or do I look at my new Prime License 500 Device upgrade LIC
    I'm looking for better documentation WCS > Prime.

    I manged to upgrade to NCS 1.1.1.24 without any problems and successfully migrate the WCS backup file into NCS.
    The next issue I have is upgrading from NCS 1.1.1.24 to Prime 1.2.
    Performed NCS backup successfully
    admin# show repository defaultRepo
    backup-20130422-0950.tar.gpg
    PI-upgrade-bundle-1.2.1.12.tar.gz
    Upgrade not successful (i'm still running NCS eval license, should I be importing Prime PAK licenses after upgrade to Prime?)
    admin# application upgrade PI-upgrade-bundle-1.2.1.12.tar.gz defaultRep                                                                              o
    Save the current ADE-OS running configuration? (yes/no) [yes] ?
    Generating configuration...
    Saved the ADE-OS running configuration to startup successfully
    Initiating Application Upgrade...
      Stage 1 of 7: Transferring file ...
      -- complete.
      Stage 2 of 7: Unpacking file ...
      -- complete.
    % One or more required RPM's not found in the bundle
    admin# show ver
    Cisco Application Deployment Engine OS Release: 2.0
    ADE-OS Build Version: 2.0.1.038
    ADE-OS System Architecture: x86_64
    Copyright (c) 2005-2010 by Cisco Systems, Inc.
    All rights reserved.
    Hostname: SV195968
    Version information of installed applications
    Cisco Prime Network Control System
    Version : 1.1.1.24

  • Upgrading WCS from 4.2.62.11 to ?

    Hello All,
    I recently purchased 6 1142 AP's and added them to my controller, well since these are not LWAP but instead CAPWAP AP's they were not supported by my WLC with code version 4.2 (not the end of the world) so I upgraded the WLC to code 6.0.182 but had to sacrifice managing it from my WCS.
    Now I would like to upgrade my WCS to support managing this WLC again and potentially upgrading my remaining WLC's, the thing is I would like to upgrade to the latest WCS version 6.0.132 but need some input as to the ease of upgading, and/or any potential problems that might surface, or if anyone is currently experiencing any issues using this WCS code. Will 6.0 be the best bet or is it sufficient to step up to 5.2? Are you satisfied with this upgrade? How many WLC and AP's are you managing? Is there anything I need to consider that isnt written in the Cisco documentation?
    Any input would be greatly appreciated.

    You do need WCS 6.0.132.0 to manage your 6.0.182.0 WLC.
    To upgrade, its easy, just make a backup of your db, run the installer of 6.0.132.0 and you will be all set. There are not really issues in the upgrade and this should go smooth.
    WCS 5.2 will not support your WLC running 6.0
    WCS 6.0.132.0 release note:
    http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN6_0.html

  • Upgrade WCS

    What are the requirements to upgrade the WCS 4.0 to 4.2?

    Hi Ricardo,
    Here is the related info;
    Upgrading to a New Software Release
    The Cisco WCS release must be the same or more recent than the controller software release. Upgrade the Cisco WCS first to prevent any unexpected problems.
    Note If you upgrade to a Cisco WCS software release later than 4.0.87.0 from a release prior to 4.0.87.0, the users, user groups, tasks, and user passwords do not migrate. Upgrading to 4.0.87.0 before upgrading to a later release migrates the users, user groups, tasks, and user passwords.
    Cisco WCS supports database upgrades only from the following official Cisco WCS releases:
    •4.0.66.0
    •4.0.81.0
    •4.0.87.0
    •4.0.96.0
    •4.0.97.0
    •4.1.83.0
    •4.1.91.0
    •4.2.62.0
    From this good doc;
    http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCSRN4_2_62_11.html
    Hope this helps!
    Rob

  • WCS 5.1 upgraded to v6.0.170.0

    Hi,
    I am in the process of upgrading the software WCS 5.1 to v6.0.170.0...The OS platform is RHEL 5.1
    Can you anyone guide me how to go about the software upgradation?....What are the prerequisitives?...What permissions are required?....
    In case some error comes back, what would be the back up plan ?
    Please help
    Thanks
    minimintu

    For Linux, you need to have root privileges to install the application as SUDO will not work.
    Here is the release notes for 6.0.170.0:
    http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN6_0_170.html
    Using the Installer to Upgrade WCS for Linux
    Follow these steps to upgrade WCS (on a Linux platform) using the automated upgrade:
    Step 1 Using the command line, perform one of the following:
    a. If you are installing from a CD, switch to the /media/cdrom directory.
    b. If you are installing from Cisco.com, switch to the directory in which the install file was downloaded. For example, if the install file was placed in /root/Desktop, enter cd /root/Desktop.
    Step 2 Enter ./WCS-STANDARD-K9-6.0.X.Y.bin (for CD users) or ./WCS-STANDARD-LB-K9-6-0-X-Y.bin (for Cisco.com users) to start the install script.
    Step 3 The Install Anywhere message appears and prepares the system for installation. After a few seconds, the Introduction appears, followed by the license agreement statement. You must accept the license agreement to continue.
    Step 4 At this point, the install wizard detects whether a previous version of WCS is installed and specifies whether the current version is eligible for an automated upgrade. You receive a notification whether or not your most recent WCS version is eligible for the automated upgrade.
    Step 5 If you cannot continue to the automated upgrade because your current WCS version is not eligible, choose Install and continue to the manual upgrade (refer to the WCS Configuration Guide for manual upgrade instructions). You can also choose to do a manual upgrade rather than the recommended automated upgrade by choosing Install and continuing to the manual upgrade, but this is not recommended. If your current WCS version is eligible for the recommended automated upgrade, choose Upgrade and continue to Step 6.
    Step 6 Several of the values from the previous installation are retained and carried over as part of the upgrade. These include the following:
    •the ports
    •the root password
    •the root FTP password
    •the TFTP server file location
    •the FTP server file location
    •the multi-homed server interfaces
    Step 7 Choose a folder in which to install the Cisco WCS. It must be a different location than the previous installation. Click Next to continue.
    Step 8 Choose a folder location to store the shortcuts. It must be a different location than the previous installation.
    Step 9 Continue to follow the prompts that appear. You are notified when the system checks for required space, uninstalls previous versions, backs up files, restores, and so on. A prompt appears asking if you are ready to start WCS as a service. Click Yes.
    Note The upgrade log is located in the standard log directory (\webnms\logs) if the automated upgrade completes. For an incomplete automated upgrade, the upgrade log is located in the user home directory.
    -nael

  • Upgrading WCS to Prime

    I'm in the process of upgrading a customer's WCS server to Prime. I know before I can upgrade the WCS server to Prime. I must first upgrade the WCS sever to NCS. My problem is the customer's WCS server is running software version 7.0.230 and I need to upgrade it to 7.0.240 before I can extract the WSC database. My question is, if I upgrade the WCS server  from 7.0.230 to 7.0.240 will that cause the customer's  Wireless Lan Controllers that are being managed by WLC server to also upgrade?

    Maurice, I had a devil of a time upgrading WCS to NCS to Prime.
    Long story short, I found the time taken on a very unsuccessful WCS->NCS->Prime migration was 4-8 times longer than the time it took to just install Prime, add the WLCs, and manually rebuild the maps.
    YMMV.
    PS, Cisco Prime LMS is probably replacing their wired management software (often LMS, Cisco Works+ RME, etc). I believe every best-practice guide I've seen from Cisco says to have one Prime for wireless, and one Prime for wired... even though Prime looks like it could handle both.

  • WCS/WLC upgrade options

    Hi,
    I'm currently running both a WCS appliance and a windows server WCS on version 4.2.62.11
    They are managing around 1000 AP's that are in a Hospital environment. They are using Vocera badges.
    The controllers are all running v4.2.61.0
    What are my best upgrade options for both WCS and the controllers? I'm looking for stability, improvements and fixes.

    We ran a pretty stable 4.0.217 for about a year with no big issues that I can remember. We started getting 1252s and needed to upgrade. We finally jumped in with 4.2.130 and had some pain. We started having issues with Vocera roaming, and Dell 1470/90 adapters had issues also. We've seen the following issues (CSCsm65043, CSCsi26248, CSCsi72578, CSCsq57697, CSCsu44970, CSCsr40109, CSCsv21441, and CSCsv21464). Some have been fixed in 4.2.173/176, but with the latest security advisory, it makes sense to run 4.2.176.
    With 19 pages of open caveats in 4.2.176, it's a crap shoot for sure, but probably the best you can do as it's a MD release. Also we have depreciated the Spectralink and only run 7921 and Vocera.

  • WLSE - WCS upgrade license question

    Hello,
    We need to upgrade our WLSE to WCS but our sales people bought the wrong license (WCS-Standard-K9) Is it possible to upgrade the WLSE to WCS with this license and just get the conversion CDs needed from you ?

    Hi Gudmundur,
    This will not work, plus you have probably paid more that is necessary as the Upgrade Licenses are le$$ to encourage this migration. You should,as noted by Dennis contact your SE or;
    [email protected]
    Converting Existing CiscoWorks WLSE to Cisco WCS Licenses
    CiscoWorks WLSE (Models 1130-19 or 1133) can be converted into a server that runs Cisco WCS. This allows customers of CiscoWorks WLSE to migrate to the Cisco Unified Wireless Network architecture using their existing CiscoWorks WLSE platform. CiscoWorks WLSE conversion SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
    Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a brand new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Stand-Alone (autonomous) access points are not supported by a converted CiscoWorks WLSE.
    All WCS-WLSE-UPG-K9 SKUs ship with two special conversion CDs. These CDs will check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The conversion software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
    Note: Please take note of the following special considerations for CiscoWorks WLSE conversions.
    CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Models 1105) are not supported with this SKU. Do not install the CiscoWorks WLSE CDs on to the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and will not work.
    A CiscoWorks WLSE that has been converted to Cisco WCS cannot be reverted back to operate as a CiscoWorks WLSE.
    To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
    Please see Appendix C for information about receiving support for existing SMARTnet® (hardware support) contracts for CiscoWorks WLSE.
    Customers that are migrating their existing CiscoWorks WLSE to operate as a Cisco WCS server should select from the WCS-WLSE-UPG-K9 SKU family and then select one of the sub-SKU options based on the following:
    Base or Location
    Access point quantity. (The CiscoWorks WLSE conversion CD's do not automatically provide support for a set number of access points or location services. The number of lightweight access points supported as well as Cisco WCS location is selected by the customer based on the WCS-WLSE-UPG-K9 family sub-SKU. Customers can select the sub-SKU that contains the access point count and Cisco WCS option that they wish to support.)
    A Cisco Ordering Tool sample for WCS-WLSE-UPG-K9 is displayed in Link.
    PAK Certificate, Instructions and CD
    Customers that purchase the SKU family WCS-WLSE-UPG-K9 will automatically receive, by U.S. mail, two special CDs containing the CiscoWorks WLSE to Cisco WCS conversion software, as well as the PAK certificate, instructions on how to register the PAK and links to Cisco WCS manuals and release notes. CiscoWorks WLSE conversion software cannot be downloaded.
    http://www.cisco.com/en/US/products/ps6305/products_data_sheet0900aecd804b4646.html
    Hope this helps!
    Hi Gudmundur,
    This will not work, plus you have probably paid more that is necessary as the Upgrade Licenses are le$$ to encourage this migration. You should,as noted by Dennis contact your SE or;
    [email protected]
    Converting Existing CiscoWorks WLSE to Cisco WCS Licenses
    CiscoWorks WLSE (Models 1130-19 or 1133) can be converted into a server that runs Cisco WCS. This allows customers of CiscoWorks WLSE to migrate to the Cisco Unified Wireless Network architecture using their existing CiscoWorks WLSE platform. CiscoWorks WLSE conversion SKUs are price-adjusted to make transitioning from CiscoWorks WLSE to Cisco WCS cost-effective.
    Once converted, a CiscoWorks WLSE is no longer a self-contained appliance; it becomes a server that runs Cisco WCS software using RedHat Linux ES v. 4.0. The converted CiscoWorks WLSE operates as a brand new Cisco WCS installation and supports only lightweight access points and wireless LAN controllers that are running Lightweight Access Point Protocol (LWAPP). Stand-Alone (autonomous) access points are not supported by a converted CiscoWorks WLSE.
    All WCS-WLSE-UPG-K9 SKUs ship with two special conversion CDs. These CDs will check to make sure that a CiscoWorks WLSE is installed prior to beginning the Cisco WCS conversion process. The conversion software will not install if the CiscoWorks WLSE software check, performed by the conversion software, does not pass.
    Note: Please take note of the following special considerations for CiscoWorks WLSE conversions.
    CiscoWorks WLSE Express (Model 1030) and CiscoWorks WLSE (Models 1105) are not supported with this SKU. Do not install the CiscoWorks WLSE CDs on to the CiscoWorks WLSE Express (Model 1030) appliance or CiscoWorks WLSE (Model 1105). This conversion is not supported and will not work.
    A CiscoWorks WLSE that has been converted to Cisco WCS cannot be reverted back to operate as a CiscoWorks WLSE.
    To find the model number of a CiscoWorks WLSE, look at the compliance label on the bottom of the chassis front bezel. Only CiscoWorks WLSE with a compliance label that says 1130-19 or 1133 can be converted to Cisco WCS.
    Please see Appendix C for information about receiving support for existing SMARTnet® (hardware support) contracts for CiscoWorks WLSE.
    Customers that are migrating their existing CiscoWorks WLSE to operate as a Cisco WCS server should select from the WCS-WLSE-UPG-K9 SKU family and then select one of the sub-SKU options based on the following:
    Base or Location
    Access point quantity. (The CiscoWorks WLSE conversion CD's do not automatically provide support for a set number of access points or location services. The number of lightweight access points supported as well as Cisco WCS location is selected by the customer based on the WCS-WLSE-UPG-K9 family sub-SKU. Customers can select the sub-SKU that contains the access point count and Cisco WCS option that they wish to support.)
    A Cisco Ordering Tool sample for WCS-WLSE-UPG-K9 is displayed in Link.
    PAK Certificate, Instructions and CD
    Customers that purchase the SKU family WCS-WLSE-UPG-K9 will automatically receive, by U.S. mail, two special CDs containing the CiscoWorks WLSE to Cisco WCS conversion software, as well as the PAK certificate, instructions on how to register the PAK and links to Cisco WCS manuals and release notes. CiscoWorks WLSE conversion software cannot be downloaded.
    http://www.cisco.com/en/US/products/ps6305/products_data_sheet0900aecd804b4646.html
    Hope this helps!

  • WCS upgrade and HTTP port open

    Hello All,
    I am trying to upgrade my Wundows based WCS 4.2.97.0 to 5.2.130.0.
    During the upgrade it tells me that port 8 (http)is needed by WCS and being used by another application. I have tried to find out which application is using that port so that I either stop the app or service and failed.
    Would anyone kow a quick way to discover/disable the app on a Win 2003 server/
    thanks a lot
    Bo

    Hi ericgarnel,
    I am not running IIS on the server. I removed the WCS 4.2.97.0 and rebooted the server. I still get the same port hhtp (port 80) is being used by another application.
    thanks
    Bo

  • WCS base upgrade to PLUS license question

    I have a 50 AP base WCS running. What kind if license do I need to order to be able to do location? These two have the same price, but can I upgrade to 100 WPLUS from 50 BASE by ordering the second one?
    L-LIC-WPLUS-50
    50 AP WPLUS  license (Delivery via Email)
    L-LIC-WPLUS-100U
    50 to 100 AP WPLUS upgrade license   (Delivery via Email)
    Thanks,
    Tao

    You would need an upgrade license to go from base to plus.
    CISCO BASE-TO-CISCO PLUS  UPGRADE FOR EXISTING CUSTOMERS (WCS-PLUS-UPG-K9)
    • If  you are an EXISTING customer who wants to upgrade from a Cisco Base to  Cisco PLUS license, order WCS-PLUS-UPG-K9 and select one of the  Cisco WCS PLUS upgrade options below:
    WCS-PLUS-UPG-50:  License supports up to 50 access points. <---------------------
    WCS-PLUS-UPG-100:  License supports up to 100 access points.
    WCS-PLUS-UPG-500:  License supports up to 500 access points.
    Note: The number of WCS-PLUS-UPG-K9 licenses purchased must equal or exceed  the number of installed WCS Base licenses for the Cisco WCS to register  as a Cisco WCS PLUS system. Thereafter, additional capacity is added by  ordering PLUS licenses.
    http://www.cisco.com/en/US/prod/collateral/wireless/ps5755/ps6301/ps6305/product_data_sheet0900aecd804b4646.html

  • Error when adding a WLC to WCS

    When adding a WLC to WCS I get this error: Failed to add device to WCS Reason:
    COMMON-1: Some unexpected internal error has occured. If the problem persists please report to the Tech Support.
    WCS 7.0.164.0 was upgraded from 5.2.110.0 because the WLC were running 7.0.98.0
    WLC4404-100 7.0.98.0 (Already in WCS)
    WLC4402-12 7.0.98.0 (Changed the ip address of the management and ap manager.  Was in WCS but deleted from WCS prior to the ip address change and prior to the WCS being upgraded)
    I know that the snmp strings are fine and that the WLC's both respond to snmp get commands.
    The intial WCS upgrade from 5.2.110.0 to 7.0.164.0 didn't require the previous version to be uninstalled.  After the upgrade and restoring the WCS from backup. I was getting the error posted above.  We uninstalled WCS and re-installed WCS from scratch and still we are getting the same error.  We tried restarting the WCS services and also the VM box as well and not luck.  I was wondering if the WCS has the old ip and mac address of the WLC4402-12 in the database and that is why i'm getting this error.
    I did delete and try different snmp community strings with no luck with WCS.  Again, snmp is working since I can do snmp get from the WLC's.

    Scott,
    This is the issue:
    com.cisco.common.persistence.transaction.TransactionException: Null value was assigned to a property of primitive type setter of com.cisco.server.managedobjects.aaa.GuestUserTemplateCG.userStatus
    Could be an existing bug or a new one. I cant say unless I look into your setup.

Maybe you are looking for

  • I just bought a book on iTunes. Where is it?  How do I find Where it is kept on my iPad

    Where do I retrieve my book after buying it on ITunes

  • Upgrade cpu or get a new laptop?

    I currently have a compaq presario cq56 notebook pc that only has the intel celeron processing unit (Sadly my mom didn't know anything about cpu or memory and just picked a random laptop for me). I am constantly running into conflicts because the cpu

  • Thinpad External Battery Charger

    Anyone use or have used the External Battery Charger?  I'm interested to know if it charges the battery to 100% or charges to the custome settings I have set in Power Manager? Solved! Go to Solution.

  • Getting blue screen when i try to do a system recovery

    hi im having problems with my hp compaq presario cq60 i currently have windows vista running on it right now and it was working fine then the other day i was on a website doing something then all my pages froze on me and i went to shut it down and re

  • Creating a standalone program

    can a program be created which will remain in dormant state until a server based program sends some message to it. After the dormant program on the client machine recievs the message it will pop-up or it will give a bip sound(prefferably bip sound).