Physical Hard Drive is shown "uninitialized" in windows server 2008 even after reboot and I am not able to initialize the disk using Disk Manager or DiskPart.
Any solution for windows server 2008. There is a hotfix 840781 addresses the issue specifically for windows server 2003. Is there a similar hotfix available for windows server 2008?
Thanks
Abhishek
I could not find any hotfix addressing this issue for windows 2008. However, I have jut updated my windows (Control Panel >> Windows Updates >> Install Updates) and issue is resolved for now.. I am not sure if this will arise in future...
Related
I have Windows 7 running on my machine, and other hand I have virtual hard disk file(.vhdx), which is creates using Windows 8. So as I know found,
Hyper-V isn't available on Windows 7 client SKUs, like Enterprise. It's only available on Windows Server 2008 x64 (some SKUs), Windows Server 2008 R2 (most SKUs), Windows 8 Professional x64, Windows 8 Enterprise x64, and Windows Server 2012 (again, most SKUs).
You've just installed the management tools which allow you to manage a remote instance of Hyper-V.
Is this correct ? If yes then is there any way i can open this .Vhdx in any other Softwares on Windows7 . Or how can I use it ?
I found below blog on "How to Restore VHD File backup" but looking for alternative way?
http://answers.microsoft.com/en-us/windows/forum/windows_7-system/how-to-restore-vhd-file-backup/f3ed3ca5-3079-40cd-a959-835caeba80a7
Thank you
Royally late ... but I had the same problem and ended up implementing it in my software.
To answer your question
is there any way i can open this .Vhdx in any other Softwares on Windows7
You can use IsoBuster to open the *.vhdx files and extract files from the image file to your Windows 7 PC. ( download: www.isobuster.com/ )
I hope this helps ?
I am trying to remote debug my application in VMware workstation 7 and Visual studio 2010 ultimate. I habe several images (win 7 ultimate,vista,etc).
I am following this tutorial: http://kristofmattei.be/2010/01/20/debugging-applications-in-virtual-machines-with-vmware-workstation-7-and-visual-studio-2008-sp1-2/
Whenever I try to start msvsmon.exe on the remote computer it will say :
"The visual studio remote debugger does not support this edition of windows"
tried it with win 7 ultimate, vista premium and xp home, same situation.
Could someone help me out here?
Thanks!
The error message "The visual studio remote debugger does not support this edition of windows" appears because the remote debugger tries to use Windows Authentication by default, and this is only supported in the "Pro" versions of Windows, and up.
However, the remote debugger does work with the "Home" versions of Windows, you just have to tell it not to use authentication via the command line.
(Why it doesn't let you do this after launching it without any arguments, why the error message is so misleading (and contradicts the official list of supported OS), and why there is so little info about this on the web, I don't know. :))
To launch it, run this:
msvsmon.exe /noauth /nosecuritywarn
Of course, this launches it in the lowest security mode, so you'd only want to do this on a secure network. (But that's usually the mode one ends up using msvcmon in anyway, as the other mode is an even bigger PITA to set up than it is normally. Very useful tool, but really could use some streamlining.)
No need to use VMWare features.
Inside the guest VM run the version of msvsmon that came with your copy of visual studio 2010 (A setup package for just the remote deubgging stuff can be found on the disc/image) (use x86 if debugging a 32-bit process or x64 if debugging 64-bit one ,Itanium if you need to laugh).
through the msvsmon GUI disable authentication and select allow any user to connect.
disable the firewall in the VM.
on the host machine you should be running visual studio 2010, under the debug dropdown select "attach to process..." and then on the window that pops up select remote from the dropdown that should say local or something initially, enter the IP address (should be private network IP i.e. 10.1.?.?) of the guest VM, alternatively use the server name displayed by the msvsmon GUI. You should get the process list for the guest and should only attach to any process that matches the version of msvsmon you ran (x86 or 64 ...or Itanium laugh).
NOTE: These are basic instructions to show you it definitely works but these instructions will only work for native code since managed requires a secure connection.
If you are debugging a .NET app using the VMWare VS Plugin and are getting a "file not found" type of error...make sure you have the .NET runtime installed! :)
Like a moron, I set up a fresh XP VM and forgot to install the .NET runtime and wasted a good day trying to get the VMWare VS Plug-In to work!
VSID is not supported by visual studio2010 http://communities.vmware.com/thread/282407
I have a Windows 2008 R2 server running on a VM machine.
My .NET service is running on this server periodically querying WMI, for example:
SELECT ProcessId FROM Win32_Service WHERE ...
After a day or two WMIprvse takes up to 500M memory and WMI queries start getting out of memory exceptions.
This article seems to be talking about this issue:
"http://support.microsoft.com/kb/958124"
I've seen other articles saying that Microsoft is aware of the problem and not going to issue a fix until the next major release.
http://social.msdn.microsoft.com/Forums/en/netfxbcl/thread/256eb40c-d050-4278-a3d8-863e30db02a0
I'd appreciate any suggestions and insights on this.
Check out both the following KB articles,
KB981314 - The "Win32_Service" WMI class leaks memory in Windows
Server 2008 R2 and in Windows 7 -
http://support.microsoft.com/kb/981314/en-us?p=1
KB977357 - A memory leak issue occurs in the Windows Management
Instrumentation service on a computer that is running Windows Server
2008 R2 or Windows 7 - http://support.microsoft.com/kb/977357
...but also worth noting we are on Windows 2008 R2 with SP1 (file versions higher than those provided by both hotfixes) and we are still seeing some slow memory leak issues possibly from either WMIAPSRV.exe and/or TRUSTEDINSTALLER.exe.
We are going to open a support call, if we find anything relevant will post the answer.
There is a hotfix available, but you have to request it by clicking on the link to request the hotfix at the top of the page.
Hotfix
Are there any limitations with respect to developing ASP.NET and WPF apps using VS 2008/2010 and SQL Server 2008 on Windows 7 Home Premium?
I know you can run IIS 7.5 on Home Premium. I Googled and Binged on Home Premium and VS/SQL Server and couldn't find much. It doesn't look like the features missing from Home Premium, domain joining, xp mode, etc... shouldn't prevent one from running and developing in VS/SQL Server.
Update
I did discover one limitation w/IIS 7.5 and it applies to all versions of Windows 7 I think. You can't create your own self signed SSL certificate specifying a name other than the machine name. You're stuck with your machine name which isn't that big a deal, but it is a change from previous versions.
Update II
You can't do remote debugging on Home Premium. msvsmon won't run at all. I can't even get it to do remote debugging natively.
Visual studio will run fine. You will be "limited" to either SQL Server Express, or SQL Server Developer edition as the mssql installer checks the OS version and will refuse to install the higher end editions on desktop OSes. Note that developer edition is the exact same as the higher end editions, except with a different license, you can only use it for development, not to run real databases.
Yes, you can, and you won't have any trouble with it.
In general, application compatibility is not affected by the edition (not version) of Windows.
I would consider what the target infrastructure (Windows/IIS, .net, SQL Server etc versions) would be if you want to deploy it...
Here is a question not directly related to programming.
Being fed up with Microsoft Windows XP Professional, and the lots of eye-candy, I want to try Microsoft Windows Server 2003 as the main OS on my development PC. (The other reason is a better version of IIS than 5.1). And knowing that Win2K3 was originally designed as a Server OS, I think that I should make it somehow more "workstation friendly".
My question is: How do I transform Win2K3 (Standard Edition most probably) into a Workstation OS? Any articles or links are highly appreciated.
PS: My development PC must run mainly MS Visual Studio 2008, MS SQL Server 2008, MS Expression Studio 2, different Oracle software (10gR2, ExpressEdition, 11g) and other little utilities (a testing framework, a subversion tool - TFS, a web browser, a bittorrent client, etc). All of this are compatible with Win2K3, as I previously checked.
Tnks
I only server OS as my workstation, I had Server 2003 before I switched to Server 2008. There's a guide you can find here http://www.msfn.org/win2k3/.
You shouldn't run into any problems. Most of windows xp drivers will work on server 2003, however, some apps won't. Especially those that check for the OS version before installing. But you shouldn't have any problems with VS2008, Expression and anything you posted.
For me the only thing that was troublesome was running iTunes on server 2003, it doesn't look as good.
And if you like the eye candy you can turn it on by starting the Theme service and changing a few settings.
You shouldn't run into any issues running those applications on Server 2003.
The last time I personally ran 2003 on a workstation the only real big change was changing the security settings of internet explorer.
If you run one of the free anti-virus software packages you may find that they will not install on a Server OS.
edit: As another poster has suggested I would also go straight to server 2008 if it is an options. Server 2008 runs very well as a workstation OS and if you're hardware supports it the virtual server works very well.
Here's links for turning 2003 into workstation:
http://www.google.com/search?hl=en&q=windows+server+2003+workstation+converter
If you'd like use Windows Server 2008 as a workstation, runs much better (faster) than a regular Vista install:
http://www.google.com/search?hl=en&q=windows+server+2008+workstation+converter&aq=1&oq=windows+server+2008+work
or try getting your hands on Windows 7 RC1 which runs quite well.
None of the software types you've listed has any workstation-biased dependencies that I'm aware of. Expression Blend may suffer a bit depending on your hardware and drivers, as WPF is a little more demanding of visual goo than most other development tools for Windows forms.