[extrabigmehdi]

Hi,
I was trying to optimise win server 2003 entreprise to be used as a workstation, as I've heard this one is much faster than Xp.
Also I was quite discouraged by the over-bloated vista, so I was looking for something more recent than xp,
without the slowness of vista (on my system..)

Anyway, I've made many try to build isos and then test them in vmware....
Then I tryed to refine settings, and to tweak all service of the system.
I've especially followed the recommendations from this site:
http://www.blackvipe.../service411.htm
All the advices were for xp pro.
Since I got win server 2003 I thought that disabling any service that's not in xp pro would be fine.
I think it is the whole new list of service added:

Quote

Application Lookup service
Kerberos key distribution center
License logging service
Resultant set of policy
Distributed file system
Virtual disk service
Intersite messaging
Mount point manager
file replication
partition manager
winhttp web proxy
Special Administration consol helper
distributed link tracking server
network provisionning service

The problem:
it seems to install fine until the system have to start for the first time after the install.
And BAM, just before I can even see my new fresh desktop I get a BSOD.

The problem does not occur if I set to default all service I have desactivated.
Here's the list of service leading to BSOD when desactivated:

[Services2]
AeLookupSvc,4
Browser,4
Dfs,4
TrkSvr,4
DNSCACHE,4
NtFrs,4
HidServ,4
IsmServ,4
kdc,4
LicenseService,4
MountMgr,4
NetLogon,4
NetBT,4
NLA,4
xmlprov,4
PartMgr,4
RSoPProv,4
RemoteAccess,4
LanmanServer,4
ScardSvr,4
sacsvr,4
LMHosts,4
Themes,4
UPS,4
vds,4
WebClient,4
SharedAccess,4
W32Time,4
WinHttpAutoProxySvc,4


See my attachements for the full settings I use.

Could you help me to tweak in a safe way the remaining setting
without having a BSOD ?

It seems I 'll give up, and leave all services as default (almost ) if I can't get an answer.
I can't make hundred try under VMWARE in order to locate why I get this annoying BSOD.

The worse thing is all that services are not needed in safe mode (using the bare minimum of services)
so then w hy without them I can't install ?


thanks

Attached File(s)

•  tell_me_why.ini (13.59K)
  Number of downloads: 4

This post has been edited by extrabigmehdi: 23 March 2007 - 01:06 AM

[dead0]

you need to leave the application lookup service as default. i had a similar problem but that seemed to work!

[extrabigmehdi]

hi dead0,
thanks for you answer, but in my case re-enabling "application lookup service" was not enough.

But I finally found.
Here are thre service required to install server 2003 if you wish not get that annoying BSOD.
1- Application lookup service
2- Mount point
3- Partition manger

The fact , is that the two last mentionned service by nlite, appear NOWHERE in my service list when running the OS.
It appears that these are hidden services which are critical. Or these aren't services, and nlite mistakenly show them as services , I don't know....

Anyway, I think that nlite should by default hide these services in order to avoid problems (just like it already does for RPC , I think).

Now I'm gonna make a fresh install of this one in my computer, and I hope I'll manage to connect to internet 'cause it appears I can't with Vmware.
.

This post has been edited by extrabigmehdi: 23 March 2007 - 10:23 AM

[Muppet Hunter]

I was getting similar BSOD's using 1.2.1 with all at default and have only just managed to install with 1.3. It's probably safer to leave them at default and adjust them after installing. Strangely, I used to remove App Lookup and just left it in and it's installed successfully (Win 2k3), so maybe this service is causing a problem. You'll end up spending longer figuring out which ones are to blame than leaving them alone!

This post has been edited by Muppet Hunter: 25 March 2007 - 07:37 AM

[LeveL]

What is the BSOD?

RDR_FILE_SYSTEM?

If it is then its because of Event Log. Sounds silly but when stripping Server 2003
out, I had to disable Event Log during install then on second to last reboot, re-enable
Event Log. I am not saying try this, but it was a wierd problem I had.

I never noticed nLite showing services that arn't there.

Mount Manager... thats a sys file mountmgr.sys thats related to System Restore,
which is not even in Server 2003.

I dunno where you were looking but nLite does not show any services under "Services"
that are not in your services.msc window when you look in the installed OS, well OK the
Beep Driver and POP3 services... but theres no Mount Manager there, see:

This post has been edited by LeveL: 25 March 2007 - 07:43 AM

[extrabigmehdi]

hi,
BSOD = Blue Screen of Death

You have the ability to remove services or just disable themm.
Usually it's safer to disable them.
The components part is about removing them.

good luck