[halladayrules]

If you plan to keep the dual boot enviornment on your machine you could always create a symbolic link to the Windows 7 user folder, provided you have privileges.

For example you can create a symbolic link at the root of the drive

mklink /d C:Windows7UserFiles D:Users%username%

This way you don’t have to waste time making duplicate copies of the same file you can just open the shortcut path to the username folder in one click.

Instead of having to navigate through the whole computer

Computer > Local Disk D: > Users > Username > “Folders”

you can just click symbolic link and its the same as clicking Start > Username in Windows

This won’t transfer your personalized settings (start menu tweaks, themes, desktop settings, etc etc but really if you think about it how long would it take to set that up? Not very long.

[halladayrules]

Well scrap that idea USMT isn’t supported in Windows Server versions.

[halladayrules]

From what I have gathered you can use the User State Migration Tool built into the Windows AIK kit for migrating your user profile from Windows 7 to R2.

You have to first download the WAIK for Windows 7 kit (1.7GB download) on the Windows 7 machine.

Next you want to use a hard-link migration so you can transfer your settings to source partition.

I haven’t used it yet so I cannot give you the syntax. I am going to install Windows 7 in a dual boot and try it out so I can give you the exact syntax to use. From what I have learned so far the syntax will look something like this

scanstate D:mystore /hardlink

Then once you have created the hard links you must install the WAIK kit on the Server 2008 R2 machine and run this syntax:

loadstate C:mystore /hardlink

The profile should be remapped automatically to your server machine hopefully.

Don’t hold me to the exact accurateness of these commands I’ve never ran this tool before.
I am going to dual boot Windows 7 ultimate on my machine right now and create a user account called Win7Admin and then try to use the USMT tool to create a hard link and then boot into server 2008 r2 and see if i can load the user profile using this tool. I’ll report back with a detailed tutorial IF i can get it to work.

[halladayrules]

I’m sorry but your only other option is to just buy a regular PCI card and unfortunately your board only has 1 PCI slot. It is possible to use a regular PCI card in a PCI-x slot but they must be the same voltage. You can tell 32-bit vs 64-bit PCI by looking at the bus… one has a short slot followed by a long slot, while the other has a long slot followed by a short one: Your PCI slot is only 32-bit while your PCI-x is only 64-bit. They are keyed differently to prevent legacy cards from fitting into them.

Picture courtesy: http://www.tomshardware.com
I see your motherboard does not have on-board sound so you would have to sacrifice sound for video if you wanted to use a regular PCI card. They are capable of supporting your resolution, but would it be worth to sacrifice sound? Your best option is probably buying the adapter and x16 card.

[halladayrules]

You need a PCI Express x16 card to adequately support that high resolution, problem is your motherboard doesn’t contain an x16 slot. You will need to buy a PCI Express X4 to X16 Adapter which will run you around $50. Next you can buy a decent but not so crazy PCI Express X16 card that supports your native resolution, but don’t go too crazy because your card will only perform at the bandwidth of the x4 pipeline. An x4 bandwidth single channel is only capable of 800MBps while a x16 card can handle 3.2GBps. I assume you are not going to be gaming so this shouldn’t be an issue.

Also, don’t forget that the adapter will raise your card on the board about a half an inch so the connectors could interfere with the chassis I/O expansion slots. Hopefully this won’t be a problem.

[halladayrules]

Aah, the loveliness of the Windows Server backup tool. I always create a baseline system state backup when I first install Windows Server. Before I even begin installing ANYTHING (drivers, roles, features, software) that way I can revert back if need be. Then once I install all theme packages, desktop experience, etc etc blah blah blah then I create another system image and write over the other one once I know it is stable.

[halladayrules]

@MRAU wrote:

😉 After searching I found very little useful information with respect to the native Burn to disk feature for server 2008 r2 so perhaps I’m the only one who cares but I thought I would share what I know just in case there’s anyone else who would rather not logon as the local admin to utilize this tool.
I found one small piece on information that suggested this was an ACL thing and suddenly a light bulb went off. I launched the Local Security Policy editor and started poking around and found under Local Policies>Security Options>Device: Restrict CD-ROM access to locally logged-on user only. I changed this value from not defined to disabled. I changed a couple of others but I think this is the one that did it. After a reboot there it was, Burn to disk. I wanted to test this to see if this was indeed the one that did but can’t seem to set it back to not defined, only enable or disable.
Anyway, if anyone else wants to test this and it doesn’t work I’ll try to back track and find the others I changed.

Try this:

Navigate to HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionWinlogon

Do you see a registry value called “allocatecdroms”? If so remove it.

Next go to HKLMSystemCurrentControlSetservicescdrom

On my machine (which has policy set to not defined)

Autorun= 1
Start= 1
Tag = 3
Type = 1

[halladayrules]

Glad I could be of assistance.

[halladayrules]

I believe I found the reason why you are getting those audit failures.

Open up command prompt and type in the following:

net user guest /active:NO

Now go to Network and Sharing Center. Click “Change Advanced Sharing Settings”

Turn On Network Discovery
Turn On File and Print Sharing
Turn Off Password-protected sharing

Save changes.

Now go to a different computer and type in the sharename of your offending computer.

For example \OFFENDING-PC

When it asks you for credentials just

After you have connected to network share close out. Notice what happens? The guest account is a Built-in system account by the operating system and by telling the machine to turn off password protected sharing you’ve told it to use anonymous access, which is why it is trying to use Guest to logon. By disabling the account you are receiving those event id 4625 audit failure errors as a result. The machine will try turn on the guest account to allow anonymous access. I had my guest account disabled and when I turned off password protected sharing it magically turned itself on. I believe this is why. I wouldn’t really put so much stress over audit failures/successes your machine will probably generate 2,000 or more of them in a couple days, why stress yourself after looking at everyone. You should really only be monitoring this if someone else has trouble contacting a network resource using an account that is supposed to be able to connect. FYI – Relax lol

[halladayrules]

I set up a little experiment. I opened up the Event Log to the Audit page which generates success/failures. Next I created a network share called “temp”, located at \STEVENTemp. Next I went to my laptop and typed in \STEVENTemp. When it asked me for credentials I put in Guest which obviously is disabled. The laptop waited for about 5 seconds and then displayed a “account is disabled” logon failure message. I refreshed the event log and I noticed that it generated about 15 audit failures all linking to the guest account. I believe what is happening is the remote computer is trying to contact the server (ACK) for a certain amount of time until it timeouts with the failed message. During its time of trying to contact the server this is why I see the consecutive audit failure messages.

Somebody or maybe yourself is trying to access a particular network resource which is set to use only anonymous access (which includes guest) and thus why you are probably receiving this audit failure.

[halladayrules]

Yeah simple file sharing just treats remote users with the same “standard” permissions. Your problem is the local account on the physical computer itself cannot use its own credentials.

Are you getting an audit failure with event ID 4625?

[halladayrules]

I had a similar problem except my logoff screen would be all black except the server logo at bottom. For me it was a corrupted user32.dll.mui file located in c:windowssystem32en-us

Did you try installing a custom theme in Windows? You may need the custom uxtheme patcher for Windows 7 as well.

[halladayrules]

@awalt wrote:

I rejoined the domain to get some work done. Should I be in the domain or still in the workgroup?

It shouldn’t matter now that we have established this isn’t a domain-wide issue its something effecting your local computer, so it doesnt matter if you are joined to a domain or not. Are you able to use the Run As command as a workaround or does it force you to always use guest?

BTW: I am moderating this forum, particularly yours so we can help resolve this annoyance. So please don’t hesitate to respond back quickly.

[halladayrules]

@byersjus wrote:

I got it working.

It was certainly never an actual memory problem (12GB RAM), but I uninstalled the demo, installed the games explorer, reinstalled the demo, and it worked.

I guess it wasn’t a completely controlled test as I should have just installed the games explorer and tried it, but I’m pretty sure that was the problem.

Someone might want to update the main tutorial and take out the part about just installing gameux.dll. I was under the impression that the .dll was required and the explorer was just frill. Apparently not.

Thanks guys!

Glad you got it working. However this still doesn’t explain why other users whom have Windows 7 with Games Explorer installed by default and plenty of RAM are seeing the same message. My suspicion is that they are not using a legit copy of the game (probably a leaked torrent) and hence are SURPRISED that the game doesn’t work.

[halladayrules]

Try this:

Reboot the offending computer and press F8 repeatedly to open Advanced Boot Options. Choose “Safe Mode with Networking”. Login with the Built-in Administrator account (not your user created one). Click on Devices and Printers, right-click Printers choose Properties. Click on the Sharing tab. IF you are allowed to continue, change the sharing permissions and give full control to the Administrators group ONLY. If you see “Everyone” remove it. Same thing for Guest, etc etc.

Now while still in safe mode go to Control Panel > User Accounts > Manage another Account

Create a new administrator account called “tempadmin”.

Now log back off and reboot as normal. First login with the offending administrator account like you always do and try to access printer sharing. Do you still receive the same printui.exe error? If this doesn’t work logoff and login with your newly created tempadmin account. Now try to do the same thing. Report back with your results.

[Author]

Posts