Kaseya Community

Patch Managment x64 windows 2003 servers

  • With the production release of exchange 2007 many customers want to upgrade exchange server. Microsoft says the 32 bit version is strickly for planning and deployment pratics and should not be used in production. Only the 64bit version is suggested by Micro$oft for production.

    So I'm seeing requests for 64 bit systems comming in. I upgraded our Offices Exchange to 2007 and installed the Kaseya Agent. But Patch Management reports

    OS not supported. (Windows 2003 Server R2 Standard x64 Edition Service Pack 2 Build 3790)

    Do we have any info on x64 being fullysupported..


    Legacy Forum Name: Patch Managment x64 windows 2003 servers,
    Legacy Posted By Username: Cubert
  • I've posted about this in another thread a few months back. Didn't hear anything back from the Kaseya folks about it then either.

    I'm very disappointed to see that this is still an issue with the 4.8 release.

    Maybe someone for Kaseya can enlightenus as to why it's so difficult to patch the x64 versions of Windows with Kaseya?

    The time for x64 is now, not years into the future. This is a greater need even than worrying about support for Vista. My clients and I are in no hurry to unleash that beast upon our networks or users.

    And there is a significant cost savings for clients to push them to the 64 bit versions of Server. You can get native support for more than 4GB of RAM with Win Server 2003 x64 Standard at the same cost as the 32 bit Win Server Standard.

    Prior to the 64 bit release you had to move to Enterprise Server which is a huge price increase.

    With the move to virtual machines RAM is king. Being able to break beyond the 4GB limit is a big thing.Especially when you can do so at the lower price point.


    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: misolutions
  • Not having a working patch management solution for 64-bit platforms is a big issue. I too am looking toward the 64-bit change. 4GB limit for Standard Server is quickly becoming a joke. 64 bit is the best way out but everyone hestitates when there management solution won't even patch it yet.

    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: connectex
  • same here

    :OS not supported. (Windows 2003 Storage Server R2 Standard x64 Edition Service Pack 2 Build 3790)

    we need some answers please


    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: oliversolman
  • I have got to agree...64 bit support is on our high priority list.... and we are having trouble bringing on new customers when they discover that we cant patch 64bit machines

    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: primalooze
  • Is patching the only thing that can't be done on the 64bit OS now? (as of 4.8)

    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: BenT
  • You also can't use VNC or Radmin for remote control. Only terminal services is supported, which many times is not adequte since true console access is often needed.


    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: misolutions
  • We use Kaseya VNCon Windows 2003 R2 Enterprise x64 edition.

    It is slow as molasses but it works.


    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: kentschu
  • Any updates on this?

    OS not supported. (Windows 2003 Server R2 Enterprise x64 Edition Service Pack 2 Build 3790)






    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: espeer
  • Bump?

    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: beedsley
  • This is a copy of an email I received from Kaseya last week. It states that there will be a hotfix available on October 19th, 2007 that will providepatch managementfor Windows XP 64 bit.

    Email Contents:

    The following is an overview of an important Kaseya product update planned for this month. This update will significantly enhance the capabilities of Patch Management. As always, we want to provide advance notice so that you have the time necessary to prepare for the update.

    Kaseya Enterprise and Managed Service Provider Edition Patch Management Update



    Overview

    A key element of Patch Management is the ability to scan a system to determine which applications are installed, compare the information to a patch database and determine the current patch status of a machine. Kaseya Patch Management uses various sources and methods to determine the patch status of a machine.

    As of the end of October, a key data source for our patch scanning engine will no longer be updated. To ensure that the Kaseya patch scanner always has timely and accurate information, we will be updating the Patch Management function via hotfix.

    In the past, an update like this was done as part of a point release or major upgrade of the system. To ensure uninterrupted support of "Patch Tuesday", your Kaseya IT Automation Framework will be updated automatically using the hotfix mechanism prior to November's Patch requirement. This hotfix is scheduled for 19 October, 2007. We will notify you when this Hotfix is available. We encourage you to familiarize yourself with the enhancements related to this release to prepare for November's patch schedule.

    In the process of making these changes, Kaseya has taken the opportunity to incorporate selected improvements and feature requests. Improvements include, but are not limited to:



    · Scanning

    · Patch Scope

    · Windows OS and Application Support

    · Approvals

    · Patch Details Popup

    · Reports

    Patch Scan Engine

    A new Kaseya patch scan engine will be deployed as part of a machine's currently scheduled patch scan for those machines having any edition of Windows 2000 SP4, Windows XP SP2, Windows Server 2003, and Windows Vista. This new scan engine includes support for all 32-bit and 64-bit versions of Windows as well as increased support for Microsoft Exchange.

    Patch Management User Interface

    The current patch technology is product and bulletin centric. It was originally created to manage Microsoft Security Bulletins for specific Microsoft products. Viewing patch data in the current product reflects this in that patch data is presented based upon products such as Windows, Office, SQL Server, Windows components such as XML core services, etc. The primary patch identifier is the bulletin ID, typically the Security Bulletin identifier (MSyy-xxx) or an arbitrary identifier generated by Kaseya.

    The new patch technology is update (patch) centric using the update's knowledge base article number assigned by Microsoft as the primary identifier and is presented based on the patch's update classification. The update classification describes the type of update such as security updates, critical updates, update rollups, service packs, etc. The screens under the Patch Management tab have been modified to support this update centric approach.

    Patch Approval

    The Patch Approval screen has been redesigned to present meaningful patch approval status data for a particular approval policy and to provide a means to drill down into the details to better facilitate approving and denying specific patches. The Patch Approval Policy Status page provides summary status data for the three different approval statuses for each different update classification. Now, with one glance, you can see the overall status of your patch approvals.

    With this update, the patch scanning will detect and identify a much broader scope of patches and applications. As a result, we recommend that the patch approval process be used. Examples of new items detected include:

    · Windows Genuine Advantage Validation Tool

    · Internet Explorer 7.0

    · Microsoft .NET Framework 2.0

    · Microsoft .NET Framework 3.0

    · Microsoft Base Smart Card Cryptographic Service Provider

    · Windows Media Player 11

    · Remote Desktop Connection (Terminal Services Client 6.0)

    · Network Diagnostic Tool

    · Vista Language Packs for Vista Ultimate

    · Vista Add-on Applications for Vista Ultimate

    Patch Scans for Legacy Operating Systems

    The current patch scan technology will be retained within the product to support all legacy operating systems that are not supported by the new patch scan technology. These include all editions of Windows 2000 SP3 and earlier, all Windows 9x editions, and all Windows NT4 SP6 editions. While Microsoft no longer provides patch management support for any of these systems, the existing store of patch data is still valid for these systems and will therefore continue to be available to update these systems to the level at the point where Microsoft ceased to provide patch support.

    Regards,

    Kaseya Product Marketing Team


    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: gssloan
  • Great news.

    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: BenT
  • As far as I can tell this update did not roll out on 10/19 as planned.

    My 64bit systems are still reporting "Operating system not supported for patching"


    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: misolutions
  • Updated info is available here.

    http://www.kaseya.com/kforum/view_topic.php?id=2897&forum_id=49


    Legacy Forum Name: Patch Management,
    Legacy Posted By Username: beedsley