Tripredacus

Seems like a misplaced post. Oh well the happy bunny says it all!

Juno Reactor - Pistolero

This sounds more like a board message. When you get this error, what is in your address bar?

Probably either Standard or Enterprise. Standard has a maximum RAM of 4GB tho. Feature Comparison

You really should consider removing this file along with the others you have included, as it is illegal to redistribute Windows operating system files.

What do you want a server to do? You might just need a NAS.

If you have Pro or Enterprise, you might be able to use AppLocker to enable those apps.

No, that was already determined to be "cheating"

I'm going to try that too, but with some OS detection since all my apps are designed to run on multiple OSes. We'll see which is the easiest to handle. Hmmm does even sending the Windows key cause a problem if another application is open? In my case there is.... sysprep.exe. Does the problem sending the key occur because that program is in focus?

Call programmatically PostMessage(HWND_BROADCAST,RegisterWindowMessage("SHELLHOOK"),HSHELL_TASKMAN,GetDesktopWindow()); after closing your messagebox. That won't work however if other windows are open on desktop. It is for me. Thanks, I'll try that. I could even just not show the messagebox I guess. You are right about the reg key, I found the issue....

Tripredacus, Can you fill me in on that one? I'm not sure how that's different from the way things are with earlier editions of Windows. The only way to get a different .NET version is via the Internet, no? --JorgeA No you are right. But there doesn't seem to be a stand-alone download for .Net Framework 3.5 for Windows 8 that I can use, instead it goes and get it from Windows Update. This is fine in a normal condition but for my work these computers never hit the internet... I do recall there is something from the ADK about it... Maybe I'll take a look-see.

This OS is full of headaches already now that I am active in working with it every day. I can't even imagine what the ODMs are going through! Here's some more "deeper depressions"... - The first boot experience is a wonder of technicolor. It has some color changing fade thing that I am now certain is the reason why it takes so long to boot. It sits around for 5 minutes "installing apps" even though there is only 1 "app" installed. I honestly have no idea what it is doing here as I wait for my squares to show up. - .Net Framework 3.5 is not available in the OS, and the only way it seems you can get it is to be connected to the internet. So any programs that require it won't run and a box comes up saying it needs it. Maybe if you are lucky, the developer has made an updated version that does't need it. So far I am 1 for 1 with this scenario, which seems way too rosy to me. - The Start Menu functionality still technically exists in the OS, which is strange since it isn't supposed to be there anymore right? For example, the OS will still run whatever is in the Startup folder after Explorer.exe launches. Since the ModernUI comes up right away, if that program is supposed to interact with the user, they won't ever see it unless they alt+tab or go to the Desktop "app" from the menu. You'd think with the Start Menu removed, the Startup folder shouldn't work... But also the entire Start Menu folder structure is still in the AppData folder, including shortcuts and everything you'd expect to see. I can see that leaving this behind would probably be helpful for legacy apps that have been adding stuff to the Start Menu for YEARS NOW... Which is not making me look forward to testing more apps! - The Runonce registry key still works, as you would expect BUT it interferes with the ModernUI opening in some modes. It makes me think that this key is deprecated now... but yet again it still works. A different change is that now the Runonce key does not de-populate itself after executing whatever is in there. So anything you actually have as being "Run Once" will run every time the OS loads. Update: The RunOnce behaviour is a little different, but it is not a problem the the registry key not being cleared. Partly a problem is due to AutoIT not being able to identify the OS properly, so some commands are not being run, specifically deleting the program that populates that registry key... hence why it appeared to not be deleted.

I've been working on porting my app installer program to work on Windows 8. I'm just about done but there is left one little issue which is mainly cosmetic. In previous version of Windows, I run a program at first boot by putting it in here: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce Windows 8 is different because it isn't supposed to boot to the Desktop, but instead show the ModernUI/Start Screen instead. It seems that if you put a program in that registry key, Windows will "sort-of" boot to the desktop. My program puts up a messagebox on the screen saying that it is done working and clicking OK will exit the program. But the screen is black with a blue (unpopulated) taskbar on the screen. I can get back to the Start Screen by pressing the Windows key, but I would rather be able to send some sort of command that puts that back up instead. So is there any other way to open/close the Start Screen without sending keypresses? EDIT: it appears that registry key is not erased at boot like in Windows 7 and earlier OSes.

Just a little update. Any client booted via UEFI PXE boot can only deploy either a single partition MBR deployment, OR a multi-partition GPT deployment. You cannot deploy a multi-partition image using MBR. At least BCDBoot can't write to the disk if it is MBR, and BCDBoot isn't used for a single (whole) partition. I'm not sure if this effects Linux at all. And still haven't found any way to detect the boot method (UEFI vs BIOS) from WinPE which could be helpful for those of us who build custom deployment systems.

I think its the drivers themselves that set the flag for the reboot prompt, or possibly any driver for a device that falls into the "boot-critical" category. I never really looked into trying to disable that notification.

In my both Windows XP computers (desktop and laptop) I can't open Windows Explorer with administrator's rights if I am in a restricted user account. Is it normal and if yes what can I do to change it? If no what can be causing it? This is normal for XP. There is no user elevation for limited accounts. However, you can add a Run-As option (in Pro or Enterprise) to the context menu BUT it still requires you to know the credentials for an administrative login on the local machine or domain.

It could also be possible to let you see drives mapped with elevated Command Prompts? I've noticed this sometimes where if you map with an elevated CMD, you can't see or can't use the the mapped drive in Explorer.

Here are some impressions of the recovery experience... - Accessing the F8 menu is difficult, if not impossible, on UEFI 2.3.1 hardware. By design, Windows disables USB input devices (such as keyboards) during boot for one... - Getting to the Recovery option is tricky and requires digging through menus. - The Refresh option is a welcome return (akin to repair install in XP) but has a habit of removing drivers, including the Realtek Audio Controller driver THAT COMES WITH WINDOWS 8! Fortunately there is an HTML file on the desktop that tells you what was removed. - The "Replace" type option that formats the drive and reinstalls Windows TAKE AT LEAST 2 HOURS! I suspect that unlike Windows 7 full recovery, Windows 8 doesn't do a quick format prior to reinstalling the recovery image.

What is the OS on the source PC and the destination PC? Just to get things clear, tell me if this is incorrect: - You plugged the HDD into the SATA port of the source computer, copied files, disconnected it after powering it down, connected the HDD to the adapter, then plugged it into the destination computer. What is the make/model of the adapter? Is it USB powered or have its own brick?

After searching for 2 minutes, it seems there might be some way to get the logs to actually show some Format Information... But regarding the actual problem, it seems the backup can fail if it encounters an Access Denied scenario caused by these possibles: - Encountered a file that is in use and/or locked by another process - some backup files were deleted during write due to another process (ie. anti-virus) Reference: http://msdn.microsoft.com/en-us/library/aa382530%28VS.85%29.aspx I would really take a look-see into Event Viewer at the time of the error-out of the Backup... which seems to be 9:00PM looking at your .ETL. And I don't just mean the top-level logs (Application, Security, System) but also drill into the ones in Applications and Services logs. You might luck out and find something in there someplace that leads you on the right track. You should also be able to find the logs created by Windows Backup when the operation fails, since you didn't post that already.

I do not get a certificate error with that website. If you go to Internet Options, Security tab, what is your setting for the Internet Zone? You can try disabling that program and see if it makes any difference.

Companies often take shortcuts when it comes to certificates. Certificates are assigned to a specific domain name, but companies will use multiple different URLs to the same website and use the same certificate which generates the error. Can you provide an example URL that gives you the certificate error that I can check?

Dell recommending nLite now? I hope this doesn't mean that Dell actually uses it!

Log file location: %WINDIR%\Logs\WindowsServerBackup Have you run CHKDSK on the F: drive? When you say you "I removed all the software from the previous It company" does this include the OS or a reinstall of it? If not, are you using the same user accounts that were on the server previous to you making the changes?

My current company bought parts of my old company and I was retained. The actual Uncle Socks hardware might still exist in one of our other locations, or maybe it was recycled. This one is in name only... BUT it is housed in the chassis from the PC called "Aaron Rules" (now named Stickers) in the first post. The motherboard from Stickers met an unfortunate kaboom a couple months ago and I had saved the chassis which was quite fortunate since I needed one to build the Server 2012 test system. The hard drive from Stickers had been transferred to a new motherboard and chassis. Oh and butwhy.com is not a real domain (you probably should go buy it now lol) and is the internal testing domain name that server sits on. I should probably have called it shark.attacksyou like the old one but oh well. I'll try to take a picture of the chassis that "Stickers" had been in an "Uncle Socks" is in now... so that you know why it was called Stickers.