Fipse

Hi,

we are running a test with WDS 3.01 and my user are loving it.

But we have 1 problem, every morning when they boot there computers it take a long time before they get to the the login dialog, if i disable the GP that controls the WDS instalations it working just fine. in my apliaction log I get the followring errors. 3036, 3023, 3024 and 1003.



Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

dA.oOZe

Same issue here. Removing GPO or WDS get the computer back for normal boot speed. This prevents me from rolling out WDS company wide.

Any suggestions





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

Andreas Baum

Hello,

try to change the start typ of the WDS service from auto to manual.





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

Fipse

Hi,

we are a the moument testing this, and it looks positiv, i'll report back in 2 days, just to be sure that it works and our test group.

can you explain why this works.

/Jesper





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

Ari Polsky - MSFT

This is a known issue. We are still actively investigating the exact cause. Changing the startup type of the service to manual should work, but it has the effect of turning off search until the user turns it on manually. You may be able to accomplish this via a logon script that does a "net start wsearch" to turn it on automatically. I'll let you know as soon as we find the best workaround, but rest assured that this in on our radar and will be fixed in our next release.




Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

Andreas Baum

Hello,

you need to start WDS in the Autostart and the service start. You needn't a net start wsearch.





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

Fipse

Hi,

when i try and start the "Windows Search" service I get the followring error.

there was a Service specifik error: 2147500053

i know it must be something wtih witch user I give access to by the GPO, the problem must the be that I can't chosse the "local System account" under the GPO. any ideas





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

Ari Polsky - MSFT

We have found a workaround for this issue. If you make the Windows Search service dependent on NLA (so that the system will ensure NLA starts first) your hang during boot should disappear. There are a couple ways to do this:

1) From a command prompt, type:

sc config wsearch depend= TermService/Nla

All this does is modify the registry value that specifies what dependencies the search service has.

2) The other way to do it is to just modify the registry directly. Navigate to

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WSearch

Double-click on the DependOnService value in the right-hand pane. In Value Data it should already have a value of TermService. On a separate line, add "Nla" (without the quotes). Click OK.

Or you can just copy and paste the following into a file with a .reg extension and double-click it and its contents will integrate into the registry:

Code Snippet

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WSearch]
"DependOnService"=hex(7):54,00,65,00,72,00,6d,00,53,00,65,00,72,00,76,00,69,00,\
63,00,65,00,00,00,4e,00,6c,00,61,00,00,00,00,00

Please let us know if this works for you or not.




Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

Andreas Baum

Hello,

the NLA Tip doesn't work for me.

cu Andreas





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

Ari Polsky - MSFT

The NLA workaround doesn't seem to be working for everyone. Another workaround is to set the Windows Search service startup to manual. The service will still be started by the search tray icon once a user logs on. The side effect of this fix is that items will not be indexed until a user actually logs on to the machine. Also, the first logon may take slightly longer than usual since the service is starting then rather than at boot time. These effects should only be an issue on first logon after booting because the service should stay is the running state even after a user logs off. Please let us know if this doesn't work for you, or if you run into any other issues as a result of using this workaround.





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

ex-ms

Hi,

I recommend as workaround to uninstall WDS and install Copernic. Nic posted about his experiences and I tried it. Perfect app, low on resources and indexing is just as fast. But no re-index on boot in addition to the better usability.

Great on resources. Brilliantly done.

There always comes a time to move on... so long!

DickS





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

TMQ

We are also running WDS 3 and have the problem that computers take 2 minutes extra to boot before the login dialog appears, if i disable the GPO that controls the WDS settings the 2 minute delay does not occur. Setting the manual service start and dependency suggested above does not solve the problem

I changed the GPO so that all settings were not configured and the boot time improved so I added each GPO setting individually and I found that any setting in the WDS3 GPO causes a 2 minute delay in logon





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

Fipse

Hi Ari,

sorry for my late reply, but ben a bit hung up in other matters.

it dosn't work for me to make the service relient of the NLA service. But it works if i manually on the machine set the service to manual start. if then set the manual start by a GPO I can't start the service. when the machine boot. i get the followring error. there was a Service specifik error: 2147500053.

any ideas

/J





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

TMQ

I also get the same error when setting the wsearch service to manual startup in the GPO, event id 7024 service specific error 2147500053 the service doesn't start manually. I have had to set back to automatic and now have the 2 minute start delay again





Re: Windows Desktop Search Development long boot time when using GP to control WDS 3.0.1

KeesFan

Same here! (Service crashes and then suddenly starts perfectly, but resulting in a very very big delay in "Applying computer settings")

Nla-tip doesn't work at my site.

Setting the startup type of the Windows Search service to manual using the GP also results in the error stated above. Service can't be started by hand anymore.

Setting the startup type of the service by using the registry editor (and a batch to deploy it enterprise-wide) makes it work! Sounds really strange.

Bottomline is that something is wrong with this service, MS please look in to this! Any news about next releases