I've done some testing.
I created an XP image with no folder redirection and the novell client
uninstalled. I was able to install Windows Defender and download and
install
the updated definitions.
Next, I uninstalled Windows Defender and changed all of the Favorites
registry entries to point to the N: drive. I rebooted and then tried
to
reinstall Windows Defender. As expected, I was not able to install the
program since I didn't have an N: drive mapped because I was not
authenticated to the Novell tree. When I tried to install the program,
right
when it was computing space requirements, I received an error that
read:
Invalid Drive N: and the install failed. There was also the same error
as
before logged in the event logs- Event ID: 11327, error 1327 invalid
drive
N:.
Next, I installed the Novell Client. I was now authenticated to the
Novell
tree and my N: drive was mapped automatically. I was now able to
install
Windows Defender successfully. However, I was not able to install the
updated definitions. I received the same error as before in the
Application
event logs- Event ID: 11327, error 1327. Also, I had an error pop-up
that
said that Windows Defender could not update because of error
0x80070643.
I hope this info helps some.
:
I think I can say that this is being looked into. It'll take some
time
to
set up a replication scenario, but it is being looked at.
I'm hoping that if you change just that registry entry on your
successful
test, that updates will now fail. That would make the likelyhood of
their
being able to replicate this pretty good I'd think.
--
Bill:
Thanks for the suggestion. I created a Windows XP image with no
folder
redirection. The client machine downloaded and successfully
installed
the
Windows Defender definitions with no issues.
I guess the real question here is this: Are the Windows Defender
developers
going to consider folder redirection in the final version? I sent a
comment/bug to Microsoft from the Windows Defender Beta website.
Basically,
they told me that the couldn't answer any of my questions because
the
software is still in beta and they directed me to this newsgroup.
I would like to use this software throughout my organization once
the
final
release comes out. Unfortanutely, we will probably have to go with
another
piece of anti-spyware software that I can actually test in our
environment
and then recommend to management.
If anyone can help or has also run into the issues with folder
redirection
and Windows Defender, please let me know.
:
That error is listed in this omnibus troubleshooting article:
http://support.microsoft.com/?kbid=906602&SD=tech#EEADAAA
You might take a look at this.
I'd recommend building a machine, or a VM without the folder
redirection,
just to be absolutely certain that WSUS is working properly, and
then
moving
on to the folder redirection issue.
I googled on the error as well, but the solutions are quite
different
depending on what's being installed, so I didn't feel I found
anything
useful--the troubleshooter may be more help.
--
Here is the windows update log that you requested:
2006-04-26 14:05:39 1424 80 AU #############
2006-04-26 14:05:39 1424 80 AU ## START ## AU: Search for
updates
2006-04-26 14:05:39 1424 80 AU #########
2006-04-26 14:05:39 1424 80 AU <<## SUBMITTED ## AU: Search for
updates
[CallId = {34CFF14D-920B-4FCE-85F0-8860D08FCC4A}]
2006-04-26 14:05:39 1424 790 Agent *************
2006-04-26 14:05:39 1424 790 Agent ** START ** Agent: Finding
updates
[CallerId = AutomaticUpdates]
2006-04-26 14:05:39 1424 790 Agent *********
2006-04-26 14:05:54 1424 790 Setup *********** Setup: Checking
whether
self-update is required ***********
2006-04-26 14:05:54 1424 790 Setup * Inf file:
C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wusetup.inf
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\cdm.dll: target version = 5.8.0.2469,
required
version
=
5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\iuengine.dll: target version = 5.8.0.2469,
required
version = 5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\wuapi.dll: target version = 5.8.0.2469,
required
version
= 5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt.exe: target version = 5.8.0.2469,
required
version = 5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\wuauclt1.exe: target version = 5.8.0.2469,
required
version = 5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\wuaucpl.cpl: target version = 5.8.0.2469,
required
version = 5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng.dll: target version = 5.8.0.2469,
required
version = 5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\wuaueng1.dll: target version = 5.8.0.2469,
required
version = 5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\wucltui.dll: target version = 5.8.0.2469,
required
version = 5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\wups.dll: target version = 5.8.0.2469,
required
version =
5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\wups2.dll: target version = 5.8.0.2469,
required
version
= 5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup Update NOT required for
C:\WINDOWS\system32\wuweb.dll: target version = 5.8.0.2469,
required
version
= 5.8.0.2469
2006-04-26 14:05:54 1424 790 Setup * IsUpdateRequired = No
2006-04-26 14:06:06 1424 790 PT +++++++++++ PT: Synchronizing
server
updates +++++++++++
2006-04-26 14:06:06 1424 790 PT + ServiceId =
{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL =
http://prod75-client1.pgh.netl.doe.gov/ClientWebService/client.asmx
2006-04-26 14:06:08 1424 790 PT Initializing simple targeting
cookie,
clientId = f8e4d6ee-bbf0-4eaf-ad03-4570f2d7bfa3, target group =
Pittsburgh
PC
Group, DNS name = pn0000021339
2006-04-26 14:06:08 1424 790 PT Server URL =
http://prod75-client1.pgh.netl.doe.gov/SimpleAuthWebService/SimpleAuth.asmx
2006-04-26 14:06:15 1424 790 Agent * Found 0 updates and 9
categories
in
search
2006-04-26 14:06:15 1424 790 Agent *********
2006-04-26 14:06:15 1424 790 Agent ** END ** Agent: Finding
updates
[CallerId = AutomaticUpdates]
2006-04-26 14:06:15 1424 790 Agent *************
2006-04-26 14:06:15 1424 790 AU >>## RESUMED ## AU: Search for
updates
[CallId = {34CFF14D-920B-4FCE-85F0-8860D08FCC4A}]
2006-04-26 14:06:15 1424 790 AU # 0 updates detected
2006-04-26 14:06:15 1424 790 AU #########
2006-04-26 14:06:15 1424 790 AU ## END ## AU: Search for
updates
[CallId
= {34CFF14D-920B-4FCE-85F0-8860D08FCC4A}]
2006-04-26 14:06:15 1424 790 AU #############
2006-04-26 14:06:15 1424 790 AU AU setting next detection timeout
to
2006-04-26 21:35:43
2006-04-26 14:06:20 1424 5a4 Report REPORT EVENT:
{4A5E731C-BBB8-4A27-A2C0-B9CD0D616E57} 2006-04-26
14:06:15-0400 1 147 101 {00000000-0000-0000-0000-000000000000} 0
0
AutomaticUpdates Success Software Synchronization Agent has
finished
detecting items.
2006-04-26 14:06:20 1424 5a4 Report REPORT EVENT:
{04236A87-FDAD-49F1-A582-370F4632A5E1} 2006-04-26
14:06:15-0400 1 153 101 {00000000-0000-0000-0000-000000000000} 0
0
AutomaticUpdates Success Pre-Deployment Check Reporting client
status.
2006-04-26 14:16:27 1424 5a4 Report Uploading 2 events using
cached
cookie,
reporting URL =
http://servername.xxx/ReportingWebService/ReportingWebService.asmx
2006-04-26 14:16:27 1424 5a4 Report Reporter successfully
uploaded 2
events.
I found that if I go through the registry and redirect every
folder
that
is
pointing to the N: drive to %USERPROFILE%, I don't receive the
error
anymore.
(Note- I was testing to make certain that the folder redirection
was
the
issue- the folder redirection cannot be changed on the image)
Instead,
I
receive a new error on the WSUS server as follows:
Installation Failure: Windows failed to install the following
update
with
error 0x80070643: Definition Update 1.14.1409.8 for BETA Windows
Defender
(KB915597).
I've tried a few of the resolutions suggested from the MS support
site,
but
nothing is working for this. I'm just concerned that this error
could
come
about later, if I ever get the updates to work with the folder
redirection.
:
I would be curious what c:\windows\windowsupdate.log looked like
when
downloading signatures.
--
-steve
Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--
This posting is provided "AS IS" with no warranties, and confers
no
rights.
Use of included script samples are subject to the terms
specified
at
http://www.microsoft.com/info/cpyright.htm
Note: For the benefit of the community-at-large, all responses
to
this
message are best directed to the newsgroup/thread from which
they
originated.
I am having a problem updating the Windows Defender Signatures
from
client
machines.
My place of employment chooses to redirct our favorites folder
to
N:\lanadmin\ie4\favorites. Our N drives are mapped to
\\server1\data\home\username. This is
accomplished by changing the registry key
HKEY_USERS\.default\software\microsoft\windows\current
version\explorer\user
shell folders\favorites to be "N:\lanadmin\ie4\favorites" on
the
client
machines.
This setup is part of our image.
However, when you do this, Windows defender cannot obtain
updates.
If
I
click "Check Now" for Windows Definitions from the Windows
Defender
Interface
