8 replies to this topic

[East17]

I have some old servers from my old faculty lab laying around and different versions of Windows Server 2003 Enterprise R2 so I thought it would be a good idea to get some of them working.

I've been scratching my head for the last day how to get AutoPatcher working. We do have both versions of the OS .. with SP1 integrated and the one with SP2 integrated but every time I click on the icon it shows the hourglass for a sec and then nothing.

First time I thought it was because I was trying to install the Italian version but on the old AutoPatcher Aug2007 CORE it does the same thing.

What could it be? I've been meddling with nLite a little and I've customized the install CDs a bit but I don;t think I've disabled something essential. Only the Windows Firewall ... CDBurning and other useless stuff.

No error ... no nothing .. just doesn't work .. no matter if its the 2007 CORE version or the latest Italian 2010 version.

[Cristiano]

please, be clear:
- you are trying update Windows Server 2003 Enterprise R2, xp, vista, seven or what? with language?
- are you running autopatcher from an local path or from an remote?
- are you running with admin rights?

[]s

Edited by Cristiano, 29 December 2010 - 08:22 PM.

[East17]

Ok ... all 3 systems are using Windows Server 2003 Enterprise R2 SP2 .

Language is English.

The patches are on the system HDD.

I'm running as the Administrator.

I've tried to install the Dec 2010 Italian version first . Nothing moved.

Then found out that installing Italian patches on an English system is not a good ideaa so I've downloaded the lastest available collection of patches . The one from Aug2007.

The result was the same ... click on the .exe and get the hourglass for half a second and then nothing.

[Cristiano]

> Windows Server 2003 Enterprise R2 SP2
so far i know, there's not an specific script for this one. some updates may work, but that's all. i'm not sure even if autopatcher is able to detect this one, but you may notice that looking at windows folder for autopatcher.log

as you know, you need update xp with xp updates, vista with vista and it's the same with Windows Server 2003 Enterprise R2 SP2

[]s

[East17]

Even the title of this forum section is : "AutoPatcher for Windows Server 2003 SP2 (32-bit)" ...

What do you mean when you say that there is no autopatcher version for Win2k3 Server 32Bit ? There is and I've downloaded it . Do you want me to post the download links ?

Or you mean that the R2 version is so much different that the autopatcher FOR Win2003Server 32Bit ,launched 5 months AFTER the release of R2, is not compatble ?

[Cristiano]

let's be clear... from our releases.list file:
AutoPatcher Updater 1.3.0.1
AutoPatcher Engine 5.6.0.100
AutoPatcher per Windows 2000 SP4 (x86) (ita)
AutoPatcher for Windows XP SP3 (x86) (enu)
AutoPatcher per Windows XP SP3 (x86) (ita)
AutoPatcher para Windows XP SP3 (x86) (ptb)
AutoPatcher for Windows Vista SP2 (x86)(don't mix w/sp1)
AutoPatcher per Windows 2003 Server SP2 (x86) (ita)
AutoPatcher for Windows 7 (x86)
AutoPatcher for Windows 7 (x64)
AutoPatcher for Office XP (English)
AutoPatcher for Office 2003 (English)
AutoPatcher Office 2007 SP2
SP1 Addon Pack for Office 2007
SP2 Addon Pack for Office 2007
DirectX Addon Pack
Extras Addon Pack
NET Framework Addon Pack
Adobe Air Addon Pack
Adobe Reader X (v10) EN-US Addon Pack
Adobe Reader X (v10) pt_BR Addon Pack
Adobe Reader X (v10) ITA Addon Pack
Microsoft Security ENU Addon Pack

in that list, where is Windows Server 2003 Enterprise R2 SP2? let's see at wikipedia

Quote

Windows Server 2003 (also referred to as Win2K3) is a server operating system produced by Microsoft, introduced on 24 April 2003. An updated version, Windows Server 2003 R2, was released to manufacturing on 6 December 2005. Its successor, Windows Server 2008, was released on 4 February 2008

furthermore, that AutoPatcher per Windows 2003 Server SP2 (x86) (ita) aims the ita version, not the english version

> Do you want me to post the download links ?
if you find the english version of it, please be my guest

> FOR Win2003Server 32Bit ,launched 5 months AFTER the release of R2
wikipedia please. Windows Server 2003 was released at 24 April 2003. Windows Server 2003 R2 was released at 6 December 2005. my calculations may not be exact, but seems that Windows Server 2003 was released about 2 years and 8 months BEFORE Windows Server 2003 R2, not after

as for not compatible, i've saw something about procedures to deploy service packs for Windows Server 2003 into R2, but what about the language? you have stated that is running the english version, not the italian version. so please, the italian updates work for the english version? something in the modules say to me that no, the modules for the italian version will not work under english. please, take a look:
[OperatingSystem]
WindowsVersion=2K3_SP1_X86,2K3_SP2_X86
SystemLanguage=1040

furthermore, i've toke an random update as an example: WindowsServer2003-KB926122-x86-ITA.exe this one says that aims the ITA version. is ms wrong in tag this one ITA instead neutral?

[]s

[]s

Edited by Cristiano, 31 December 2010 - 12:10 AM.

[East17]

I understand that the ITA version is not compatible with my English version .

What I was trying to do is install this version :

Quote

AutoPatcher Archive » AutoPatcher_Win2K3_May07_x86_ENU_Core.exe
AutoPatcher Win2K3 May 07 Core
Date: 18/08/2007 - View Full Info - Downloads: 848 - Download AutoPatcher_Win2K3_May07_x86_ENU_Core.exe (226MB)

This is made some months AFTER the release of Win2k3 Server R2 SP2 so I thought it might work .




I've been using the 32 Bit WinXP SP2 autopatcher from May2006 with WinXP SP3 for years now and it works with no problem. It sees that some updates are no longer needed .. only 5 or six of them remain checked and I was using it to get the registry tweaks and some of the addons like WMP10 installed in one move.

Thats why I've thought that an Autopatcher made for Win2k3 server 32 Bit English would work for the Win2k3 32 Bit English R2 SP2 version ..

I was thinking that the program would act like the WinXP Autopatcher. Detect that some updates are no longer needed but still work.


Can I do something to help make the ITA version work on the English version ? I mean copy/adapt the scripts and replace the patches with the ENG version... I'm not a programmer but if I need something and I have an example to work on ... I'd try to get it working for me too. Or its too complicated ?

Attached Files

•  autopatcher.jpg   173.47K   2 downloads

[Cristiano]

> Win2k3 Server R2 SP2 so I thought it might work
it only will work if the detection works. i'm not sure if the detection is the same for both or isn't. an idea: take a look at windows\autopatcher.log. that file can state if autopatcher is able to detect Win2k3 Server R2 SP2 or not. if possible, please post the content of that file in here

> only 5 or six of them remain checked
or doesn't apply at all, because they may have being replaced by something else

> WinXP
more like seven than xp. the detection for xp was included long ago. the only thing that has changed was the service pack. as for R2, the detection himself could have change

> Can I do something to help make the ITA version work on the English version ?
yes, but it's an hard work. you will require download the script and replace all the download locations, sizes, etc. but for local usage, the task is far more simple. you will require download all the updates and replace the ITA version by the same kb by the proper language. then, an renamer will help with folders and file names, but still you will require edit certain fields in the modules in order to work. but this is the easy part

> I'm not a programmer
that isn't required. anyone can update any script, with patience and will to learn how to

> Or its too complicated ?
not at all, just takes time. it will help if you target an task, like "i will update the script and the modules" or "i will update just the modules". one of those tasks is more easy to do, but it may help just you. to the other task, you will work for someone that you doesn't know as well

but don't try anything without be sure that autopatcher can detect R2. so please, check windows\autopatcher.log first

[]s

[_def_x_]

Hi East17 There's more than one way to skin a cat, I'll give my opinion. Btw, as I'm writting this I can see Cristiano has posted - hopefully we are in agreement

Quote

What I was trying to do is install this version: ...AutoPatcher_Win2K3_May07_x86_ENU_Core.exe ...the 32 Bit WinXP SP2 autopatcher from May2006 with WinXP SP3

A couple things with this, first, these are very old, no longer supported by AutoPatcher, could be filled with malware or viruses, and illegal per Microsoft (the bundling of their updates, Microsoft requires their updates be downloaded directly from Microsoft servers - hence, the reason for APUP as a download tool and the use of a script file.)

The fix for your XP SP3 is easy and way overdue - download AutoPatcher for Windows XP SP3 English ASAP - Read This Post! There are numerous reasons for this - AutoPatcher has been updated, you will also get APUP, and your XP SP3 release can better patch your system - don't hesitate.

Quote

Can I do something to make the ITA version work on the English version? ...adapt the scripts, replace the patches with the ENG version ...Or is it too complicated?

You probably can't use the script for more than an example, in fact, if you only want to build a release for yourself you don't need a script - you will need to understand the apm file and how it interacts with the update and AutoPatcher. The first step with your server machine is to find out if AutoPatcher will properly detect the OS, run, and install any updates. If I was you I would test a few AutoPatcher executables and see which version works - hopefully the latest. Do as Cristiano has mentioned, run AutoPatcher (don't try to install anything) then close the app and check the log file. It should have a few lines at the top about the Server 2003 OS, service pack level etc.

Once you determine that you can infact use AutoPatcher to install updates then you need to compile a list of the updates you need, then begin creating an apm file for every update you will add to your Server 2003 release. I would suggest first looking hard at the apm files for the XP updates (open them in notepad) - if you think you can gather the needed detections and so on you should have no problem building a custom release. You will have to live with the warning - Unofficial / Unsupported - but if you've built the release there is no worry here.

Now, the time consuming part will be to consult an appropriate list (the Ita script may be a start) to determine what updates are needed to bring the Server 2003 OS up to date. You might start with a fresh OS install, use MU or WU to see if this will get you a list of updates and hopefully available links. You might also try MSFN and look for the HFSLIP tool, there was a server version for a while, this list might be a guide as well.

AutoPatcher is one of the best tools still available for updating a system, most of the tools are overly complicated. Those of us who try to encourage more users to create custom scripts - scripts that might make it to the releases.list - know all too well, 99.999 percent flake out and never follow up with a progress report so don't expect too much help unless you're for real - we have spent hours offering assistance and most of the time the user simply quits talking about it.