fizban2

ok, fixed issue, no trying to build unattended file, scarneol, did you have to work with anything special to get the unattended file to open properly?

connect.microsoft.com. you have to be part of the beta to test it, it is still in the beta stage

i know i can't see it on my connect site but that is cause it isn't tied to my works MS account, the one at work has it after we got our TAM to add us into the PE beta

the WAIK wasn't released to everyone, select members recieved it, MSDN members i believe could get it, gadget contact your MS TAM and talk with them about getting access to PE 2.0, they should be more then happy to help you get ahold of it

garr and now i have the same issue again, cannot create a catalog file for my WIM.... stupid WSIM, scarneol, were you ever able to get WSIM working on 5308?

hrm, my vista box crashed today and i need to rebuild it, i will compare this to mine tommorow adn let you know what i get

vista uses a xml file based unattend file that can either be custom wrote or written by the windows system image manage (WSIM) which is part of the WAIK, the unattended file can do everything that can be done in XP plus a couple things after that it is very cool, ximage actually has nothing to do with proccess, it is just teh new delivery engine for vista

can you post the info from your xml file?(minus the Cd-key of course )

the core of 2003 is always going to be recogonized as a Server product, the server to wrokstation conversion does nothing more then strips out everything server related to server 2003, when software is installed it recogonizes the machine as a windows 2003 server

zartach, that number in your post the M262177 is a KB article at EventID, if you have an accoutn you could look at it and see what the resolution was, i think memmnoch would appreciate it

Now do you really want them logging on to multiple machines at once? that is going to lead to files being replaced if they are opening the files on different machines like that. if you were worried about the clients files being corrupted by being logged onto multiple machines you could always set it to allow only one logon per user, there was a post on that previous. do a search and you can find it

ADMT2 is a migration tool that should help (google it), there are dozens of guides out there for moving from NT to 2000, shouldn't be hard to find one

if you are going to do a migration why not go to 2003?? going to 200 would be a stopgap method as it is already 6 years old, you would be better off going to 2003 Server NT to 2003 migration

work him/her over good you need these new tools

unless the ram is bad, removing one stick isn't going to help much, best bet would be to check for BIOS updates for the motherboard, Nforce 4 had had issues with Vista, driver updats have seemed to help many with that issue, besides the fact that you can't just take out one stick of ram, computer wouldn't work, dual channel ram works over 2 slots, which is why the ram is in pairs.

like on the link i posted above chili

you won't find it on the CDs MS uses the Ximage APIs in their installs rather then ximage itself, you will need to the get the Vista WAIK with PE 2.0 to get it

huzzaah for learning something new. wow i just read the articles as MS on SPNEGO, lol i know nothing....

didn't know that, interesting bit of info. so from here memmnoch could check the svchost based on the PID and see what proccess is running and check permissions that are being used by the proccess to logon?

The errors also occurred after upgrading to Windows 2003 Service Pack 1. The error would be generated every second continuously on the SQL server whenever a user was connected to the server via SQL Enterprise Manager, SQL Analysis Services, or when users tried to connect remotely via the Computer Management console. After following the KB article M907460, the problem was solved. <a href="http://eventid.net/display.asp?eventid=560&eventno=57&source=Security&phase=1" target="http://eventid.net/display.asp?eventid=560&eventno=57&source=Security&phase=1"></a> they have the same issue but silly event ID want you pay them to look and the anwser wow a slow day at work From a newsgroup post: "The 537 event is common when Kerberos fails. The operation will not necessarily fail, as the Kerberos failure might be followed immediately by a successful NTLM logon (look up "SNEGO" on MSDN to see how we try Kerberos first, then NTLM, for many authentication operations). There are two likely reasons why this occurred: 1) No explicit Kerberos trust between the domain containing the machine doing the accessing and the domain containing the machine being accessed; in other words only an external trust or no trust between the domains. 2) The SPN for the target machine was unavailable to the requesting machine, at the time of the request. This could be due to a lack of routing hints on the trust, or due to the absence of the SPN in the directory. The SETSPN utility in the Windows 2000 Resource Kit can be used to see if the SPN is in place, and to re-register it if not (SETSPN.EXE -L COMPUTERNAME)". From a newsgroup post: "If you are using protocol transition, this means you have to satisfy the following requirements: 1) The Domain must be in Windows 2003 native mode. 2) Act as part of operating system (TCB) privilege has to be granted to the process that calls “WindowsIdentity” on the front-end machine (where the code runs) and not on the domain controller. Please see the Kerberos protocol transition whitepaper for more details on these requirements". again off the EventID.net webpage, good info there.

possibly when 2 dba's are trying to work with EM on the cluster at once? either connecting or editing 537 Failure Audit Logon Failure: Reason: The NetLogon component is not active 560: Success Audit Object Open From your logs we have the Audit of the object happening first trying to initiate something with the svchost, 13 seconds later the logon error occurs, could one user is trying to attach to a DB or node that is in use or locked for editing? throwing ideas out but trying to get the think tank started

Win NT paged pool errors bah, i had looked at this yesteday about that paged pool errors, no point in asking about the swtiches now as it seems to be figured out. we need more interesting questions like this. makes me think more

here are some settings to try domain security policy is where these reside, you should be able to setup something here, not sure it will do all you want though

no luck, only found issues with older NT issues, seen others have that issue, but never saw a resolution for it... have you tried the KB articles that apply to the error. i know the state for NT and 2000 but it might help, i will try and find the KB articles i saw again is there a backup client being used on these machines? backup exec etc? also what AV do you guys run? Norton? mcAfee?

Microsoft Server 2003 R2 homepage here you go, lots of good info here