software fails to write to C: with Win2003 limited user "out of disk space" - windows-server-2003

software fails to write to profile folder stored in C: with Win2003 limited user due "out of disk space"
When I look with Admin rights, there is plenty of space on C: drive
When I go with limited to user to cmd.exe and say dir c:/ , its 0 bytes free

Looks like there is a disc quota in place.

This article explains how to setup user disk quotas in Windows SBS 2003 and Windows Server 2003.
Managing Disk Quotas in Windows Server 2003 and Windows XP has more information about setting quotas programmatically.

Related

Taking a Hyper-V Snapshot of a Running Non Virtual Server?

A friend of mine asked me if it's possible to take a hyper-v snapshot of a running (Non virtual) windows 2012 server (Which I think also runs SQL Server). He wants to be able to run and experiment with the Snapshot in the event that the server goes down.
Thanks,
Ole
Yes, It is possible with the tool Disk2vhd.
Disk2vhd is a utility that creates VHD (Virtual Hard Disk - Microsoft's Virtual Machine disk format) versions of physical disks for use in Microsoft Virtual PC or Microsoft Hyper-V virtual machines (VMs). The difference between Disk2vhd and other physical-to-virtual tools is that you can run Disk2vhd on a system that’s online. Disk2vhd uses Windows' Volume Snapshot capability, introduced in Windows XP, to create consistent point-in-time snapshots of the volumes you want to include in a conversion. You can even have Disk2vhd create the VHDs on local volumes, even ones being converted (though performance is better when the VHD is on a disk different than ones being converted).
The Disk2vhd user interface lists the volumes present on the system:
It will create one VHD for each disk on which selected volumes reside. It preserves the partitioning information of the disk, but only copies the data contents for volumes on the disk that are selected. This enables you to capture just system volumes and exclude data volumes, for example.
Note: Virtual PC supports a maximum virtual disk size of 127GB. If you create a VHD from a larger disk it will not be accessible from a Virtual PC VM.
To use VHDs produced by Disk2vhd, create a VM with the desired characteristics and add the VHDs to the VM's configuration as IDE disks. On first boot, a VM booting a captured copy of Windows will detect the VM's hardware and automatically install drivers, if present in the image. If the required drivers are not present, install them via the Virtual PC or Hyper-V integration components. You can also attach to VHDs using the Windows 7 or Windows Server 2008 R2 Disk Management or Diskpart utilities.
Note: do not attach to VHDs on the same system on which you created them if you plan on booting from them. If you do so, Windows will assign the VHD a new disk signature to avoid a collision with the signature of the VHD’s source disk. Windows references disks in the boot configuration database (BCD) by disk signature, so when that happens Windows booted in a VM will fail to locate the boot disk.
Disk2vhd runs on Windows Vista, Windows Server 2008, and higher, including x64 systems.
Command Line Usage
Disk2vhd includes command-line options that enable you to script the creation of VHDs. Specify the volumes you want included in a snapshot by drive letter (e.g. c:) or use "*" to include all volumes.
Usage: disk2vhd <[drive: [drive:]...]|[*]>
Example: disk2vhd * c:\vhd\snapshot.vhd
Note: Physical-to-virtual hard drive migration of a Windows installation is a valid function for customers with Software Assurance and full retail copies of Windows XP, Windows Vista, and Windows 7. Software Assurance provides users valuable benefits—please contact Microsoft Corporation for further information. Windows XP, Windows Vista and Windows 7 installed by Original Equipment Manufacturers (OEM) using OEM versions of these products may not be transferred to a virtual hard drive in accordance with Microsoft licensing terms.
From: Technet.microsoft.com

Windows Server 2012 - alert on low disk space

How can I configure to receive an email on low disk space? I'm using Windows Server 2012 and after Googling for a while I couldn't find a way to do something that should be really simple.

Install software on Windows from Linux live usb

I'm a (noob) administrator of a little network. For business purpose I have some Windows 7 PCs and a 2008 Server.
While doing the setup, something has come to my mind: is it possible for a user without high privileges to install some kind of software using a live usb?
Ok, it's possible to reset admin password, manage partitions, etc. but can someone do that without change admin settings? just putting software in admin's (or else) directory and editing the windows register?
Thanks!
I would say: Yes. If someone manages to boot the machine from a live usb-stick, cd, dvd or whatever, he can:
Mount the disk with the windows-installation.
Read and Write to that disk.
Install software on that disk: Installing software is not much more than copying files from one place to another.
Possibly modify the registry: The registry must also be stored somewhere on the disc. If the user can access that file, he can modify it and therefore modify the registry (its another question if this are valid manipulations).
You can prevent access to the harddisk by using Windows 7 BitLocker.
It is not possible to mount the drive from a live system when it is activated:
Here is a guide how to do this:
BitLocker Guide

Mounting the WP7 VHD file

According to wiki, VHD (Virtual Hard Disk) may contain what is found on a physical HDD, such as disk partitions and a file system, which in turn can contain files and folders.
I have found the VHD image of the WP7 in the following directory.
I read that Hyper-V features offline VHD manipulation, providing administrators with the ability to securely access files within a VHD without having to instantiate a virtual machine. The Windows Disk Management MMC plugin can directly attach a .vhd as a drive letter in Windows 7. I tried the same thing.
The result was this error.
Now, I want to know if there is anyway to mount this VHD and explore the file system ? I mean can I take this VHD to a linux environment and explore ? Is this VHD really corrupt or I lack some access privileges ?
I have tried it too, but get the same message as you get. Probably a kind of restriction Microsoft has build in to protect users from sniffing around. (Especially in the period that there where no hardware devices and only the emulator was available or periods where the updated SDK is delivered earlier than the actual update)
If there is a way too mount this VHD than they definitly know how to do it at the XDA developers forum. I think posting your question overthere will result in more/better answers than on StackOverflow which has more focus on application development.

how to get correct physical memory and virtual memory

I use this windows API,
http://msdn.microsoft.com/en-us/library/aa366589(v=vs.85).aspx
GlobalMemoryStatusEx to get memory information
my computer total physcial memory is 4096MB ,why the program shows 3.XG
My computer's virtual memory is 3063MB ,but i use program which show 2047MB
my develop enviroment is visual studio 2008
how to modify this problem
thanks
Aren't other programs using your system as well? I suspect the memory you're "missing" is due to the OS itself and whatever other programs you're running. See if having a bunch of other applications open changes the virtual memory size that your program is able to see.
Assuming you are running a 32bit version of windows, then this is a limit of windows itself. See this Microsoft page for the details. By default you will only be able to access 2GB of RAM in a single process. There is a compiler switch in visual studio which will give you access to 3GB. This is the /LARGEADDRESSAWARE switch. Beyond that you just need to upgrade to a 64bit operating system.
By the way, the basic reason why you don't automatically get 4GB of address space is because part of it is reserved for the operating system. Those system calls and references to operating system resources have to live somewhere.

Resources