Forums  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Member List  Search  FAQ  Ticket List  Log Out

 

RE: Unable to deploy custom patches

 
Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [Networking & Security] >> GFI LANguard >> RE: Unable to deploy custom patches Page: <<   < prev  1 [2]
Login
Message << Older Topic   Newer Topic >>
RE: Unable to deploy custom patches - 9.Sep.2003 11:32:00 PM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
all LNSS does is put the file on the system and schedule it as a scheduled task, it might be an issue with the SFX file itself. But will try to remember that in case anyone else runs into the problem.

eric

(in reply to cwelhous)
Post #: 16
RE: Unable to deploy custom patches - 15.Sep.2003 12:31:00 PM   
Guest
We are having the same problem. We run the paid version: 3.3 Build 20030716

Upon patch push I get:

Connecting to \\P02105\C$
Connected to remote computer.
Creating patch directory : \\P02105\\system32\Patches
Unable to create patch directory. Using WinDir\System32 directory for patch storage!
Copying patches to \\P02105\\system32 ...
Copying patch W2KSP4_EN.EXE (1 left to go) ...
Unable to create file \\P02105\\system32\W2KSP4_EN.EXE - Patch skipped!
Creating batch file deploy_patches.bat ...
Unable to create batch file (deploy_patches.bat)!

where P02105 is one of the target PCs.

However, from a "run" window i can type \\P02105\c$ and I get the folder where I have full access-can create/modify/delete files and folders. What gives?

Help! I have 800 more PCs to patch and this is not working very well so far.

Thank you in advance.

Alex Jablenski

(in reply to cwelhous)
  Post #: 17
RE: Unable to deploy custom patches - 15.Sep.2003 12:58:00 PM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
quote:
Creating patch directory : \\P02105\\system32\Patches
Unable to create patch directory. Using WinDir\System32 directory for patch storage!

have never been able to reproduce this issue myself, but a few questions:

1. What credentials are you using? Existing credentials or specific credentails?

If you are using specific credentials I'd advise loggin in locally as whatever you are using as specific credentials and changing over to exising ones. We've seen issues where windows sends existing credentials even though you tell it to use specific ones.

2. What version exactly, click on Help > Current version, 3.3 20030716 is the latest released build.

3. In some cases people have been fine once the patches directory is created by hand on the machine (granted not a good fix by any means expecially with a lot of machines).

there are a few other things we'll want to check too, but try #1 first after a reboot of your machine.

eric

(in reply to cwelhous)
Post #: 18
RE: Unable to deploy custom patches - 15.Sep.2003 2:49:00 PM   
Guest
i tried both- existing credientials and entering a domain admin domain\username and password. same result in both cases.

every now and then i get another bazar error which amounts to "the user cannot connect twice to the same computer using different user names" whatever that means

i am running the latest version - 3.3 20030716. i also tried installing the software on a 2k professional os and i got the same results.

creating the installation directory on the target computer is... well not exactly a suitable solution in my case.

thanx in advance

alex jablenski

(in reply to cwelhous)
  Post #: 19
RE: Unable to deploy custom patches - 15.Sep.2003 2:58:00 PM   
Guest
Connecting to \\P02109\C$
Connected to remote computer.
Creating patch directory : \\P02109\\system32\Patches
Unable to create patch directory. Using WinDir\System32 directory for patch storage!
Copying patches to \\P02109\\system32 ...
Copying patch remote.bat (1 left to go) ...
Unable to create file \\P02109\\system32\remote.bat - Patch skipped!
Creating batch file deploy_patches.bat ...
Unable to create batch file (deploy_patches.bat)!

now, please notice that the UNC does not look right... so creating the patch directory by hand (i just tried it) does not work either.

i really really need help with this...

regads,
alex jablenski

(in reply to cwelhous)
  Post #: 20
RE: Unable to deploy custom patches - 15.Sep.2003 3:21:00 PM   
Guest
update:

i noticed that if i enable "check for missing patches" and scan, then i can update systems successfully (and path in the update report shows correctly).

does this make sense? i hope i am explaining it ok...

unfortunately, scanning for patches every host is not acceptable since it takes a while and if i enable it i will be looking at 50+ hours for the initial enumeration of PCs.

(in reply to cwelhous)
  Post #: 21
RE: Unable to deploy custom patches - 15.Sep.2003 3:23:00 PM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
quote:
every now and then i get another bazar error which amounts to "the user cannot connect twice to the same computer using different user names" whatever that means

this is a lovely issues problem, if you look up the exact error message at microsoft you can find out more about it, but this is by design in from the microsoft OS, this is not a LNSS issue.

As for:
quote:
Connecting to \\P02109\C$
Connected to remote computer.
Creating patch directory : \\P02109\\system32\Patches
Unable to create patch directory. Using WinDir\System32 directory for patch storage!
Copying patches to \\P02109\\system32 ...
Copying patch remote.bat (1 left to go) ...
Unable to create file \\P02109\\system32\remote.bat - Patch skipped!
Creating batch file deploy_patches.bat ...
Unable to create batch file (deploy_patches.bat)!

You are correct, it is not working correctly for some reason, it should look like:
\\P02109\C$\winnt\system32\Patches

it is not able to determine where your windows installation is.... ?????

will pass it onto the development team. Do you have any specific security settings? Something that does not allow remotely determining where windows is installed? Seems like this might be a security policy, but will forward it on. Will be tomorrow most likely since the people I'm sending it to are over in Europe and most likely gone for the day.

eric

(in reply to cwelhous)
Post #: 22
RE: Unable to deploy custom patches - 15.Sep.2003 7:14:00 PM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
quote:
i noticed that if i enable "check for missing patches" and scan, then i can update systems successfully (and path in the update report shows correctly).

does this make sense? i hope i am explaining it ok...

unfortunately, scanning for patches every host is not acceptable since it takes a while and if i enable it i will be looking at 50+ hours for the initial enumeration of PCs.

For LNSS to patch the systems it must do the initial check for missing patches, that is the way it is designed.

From another thread to speed up scanning for patches you can try:

quote:
If just scanning for this one, there are other changes that will speed you up. i.e. Scan/Scan Operations: Select only NetServerGetInfo and Querying Registry. Scan Options/Scanning: Uncheck port scanning options and uncheck SNMP queries. Scan Options/Alerts: Leave Alerts probing enabled checked, but uncheck everything else under it. etc..

The above is from OldManUnder in the following thread:
http://forums.languard.com/cgi-bin/ultimatebb.cgi?ubb=get_topic;f=1;t=000726

But anyway, only way to push patches with LNSS is to do the inital scan to find out what is missing, then LNSS will only push what is needed to the machines.

eric

(in reply to cwelhous)
Post #: 23
RE: Unable to deploy custom patches - 15.Sep.2003 8:03:00 PM   
Guest
i see- it makes sense when deploying windows patches and SPs... but what if i am pushing a custom patch? the state of the patches is irrelevant- no?

i would like to be able to push custom patches to a machine that I have not scanned for patches. is this something worth considering for the next release?

if you have a few machines, then scanning them for patches is not a problem. but if you have 1000 machines - it will take _forever_ to scan them. i am aware of the ways to speed up the scan, but all other options take about 10% of the time- the rest is patch scanning. one workaround is to put a mssecure.xml that scans only for one patch- this way the scanning will be faster, but ideally it would be nice to be able to circumvent that whole ordeal.

thanx in advance

alex jablenski

(in reply to cwelhous)
  Post #: 24
RE: Unable to deploy custom patches - 16.Sep.2003 12:11:00 AM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
yeah, when I was posting my last response that is what I was thinking about too, assuming your custom patch does not require a specific SP level.

I'll pass it onto development tomorrow when I have my mail program.

eric

(in reply to cwelhous)
Post #: 25
RE: Unable to deploy custom patches - 16.Sep.2003 9:04:00 AM   
xnih

 

Posts: 2465
Joined: 30.May2001
From: Idaho
Status: offline
you ask, they answer... [Smile]

I guess this is already planned for the release that is due out here shortly (might not be this week, but due out in the very near future). Basically you should be able to push custom patches without doing the full scan. Haven't seen it yet, so we shall see.

eric

(in reply to cwelhous)
Post #: 26
RE: Unable to deploy custom patches - 7.Oct.2003 8:14:00 PM   
madman0

 

Posts: 3
Joined: 7.Oct.2003
Status: offline
i am in a 2000 domain and have the exact SAME problem (on latest version /demo mode)... is there a fix??? at all for this??

i recommend this solution for my client, and was just about to do final check up before paying for unlimited license version.. and run ito this no C$ problem... is that something i need to look at teh registery?? my base machine is w2k pro, but target is xp pro, please advice.

[QUOTE]Originally posted by <Alex Jablenski>:
[QB]Connecting to \\P02109\C$
Connected to remote computer.
Creating patch directory : \\P02109\\system32\Patches
Unable to create patch directory. Using WinDir\System32 directory for patch storage!
Copying patches to \\P02109\\system32 ...
Copying patch remote.bat (1 left to go) ...
Unable to create file \\P02109\\system32\remote.bat - Patch skipped!
Creating batch file deploy_patches.bat ...
Unable to create batch file (deploy_patches.bat)!

(in reply to cwelhous)
Post #: 27
RE: Unable to deploy custom patches - 7.Oct.2003 8:24:00 PM   
madman0

 

Posts: 3
Joined: 7.Oct.2003
Status: offline
btw, the registery entry have show from Languard's window that the target machine is "c:\WINDOWS"...

(in reply to cwelhous)
Post #: 28
RE: Unable to deploy custom patches - 7.Oct.2003 8:53:00 PM   
madman0

 

Posts: 3
Joined: 7.Oct.2003
Status: offline
yeah i fix it !

it is a corrupted install of the demo.. or at least as i scan beyond 25 ip addresses.. it run into a BROKEN mode...

eventually my demo copy corrupt the xml database.. to a point it can't found it any more.. so i uninstall.. and re-install!

now it is working 100% .. i can remote deploy as well as custom patch! so if you run into my problem of no C$.. just uninstall, and reinstall!

(in reply to cwelhous)
Post #: 29
Page:   <<   < prev  1 [2]
All Forums >> [Networking & Security] >> GFI LANguard >> RE: Unable to deploy custom patches Page: <<   < prev  1 [2]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts