I have a user at one of my sites that is having an issue. We upgraded his Win 7 Home Premium to Win 7 Professional using MS upgrade via the Anytime Upgrade on his laptop. Everything seemed to work ok, however, once he logged into the network his local drive was limited to the network user's 10 gig limitation. The network is a Win 2000 based AD network. All users have a 10 gig limitation on the network drives. I didn't set this network up so I have no idea what the original admin did. I went into this particular user's profile account and took off the 10 gig limitation for him. Everything seemed ok until I get an e-mail this morning saying he's still having issues with drive space. I'm assuming he is back to getting a 10 gig limitation on his local drive via his network login somehow. Is this an issue anyone has seen before? I'm a little lost as to why the local drive would be limited to the network's drive limitation, if that's the case. It's been a little while since I played around with AD so maybe I'm missing something in his account profile that could be causing the issue? I noticed that my business laptop also somehow was only seeing 10 gig when I logged into that network with a new ID. What am I missing?

What do you see on his computer when you log in with your account. I am not aware settings that limits the space on the local drive. What do you see when you run this on his computer: diskpart list volume exit Also can you verify the amount of free space the user has on his disk?

The last time I saw the laptop, which was a few months ago, disk management was showing only a 10 gig partition for the entire drive. The drive itself is something like 200 gig and there were no issues like this before we did the upgrade and logged him into the network. My login on his laptop also showed 10 gigs under both disk management and explorer. I thought it was a fluke so I logged into the network on my own personal laptop with my network login and I got a 10 gig limitation on my local volume as well. I can verify that there was more than 100 gig left on the volume, taking into account the user's factory install and everything he had on it, before we started seeing this problem. I haven't tried "diskpart, list volume" on that laptop yet but I will when I see it in a few days. I'm researching before I get there as to what I might be able to look at or try in order to get this worked out. The user is asking about rolling back to Win 7 Home because of "issues" with Win7 Pro but he will most likely not like the fact of doing a complete re-install of the factory image. I appreciate the help!

Okay if that is the case then Disk quotas are probably enforced in your domain. If you logon to the domain and check out if there are any group policies that enabled disk quotas. It is configured in "Computer Configuration > Administrative Templates > System > Disk Quotas" You can disable the policy on the domain level, or if you just want to exclude this one user you can place an exclusion on this policy.

Thanks JBrasser! I'll take a look at that.

UPDATE - Had a chance to look at the laptop this afternoon. I confirmed that the user was excluded from the domain level disk quota, however, upon digging a little deeper into the local machine, I found that the local disk quota was causing an issue. It seems that the first network login, after upgrading from Win7 home to Win 7 Pro via the Anytime Upgrade, changed the local disk quota service and mimicked the domain level 10 gig limit. In Windows Explorer and in Disk Management, the local drive was showing a "normal" disk volume of 120gig used and 200gig free. However, upon trying to install an update or any software, an error would generate saying there was no disk space. The error was "error:80070070". I ran disk part, ran a check disk, scanned for malware/spyware/av and everything was giving me normal status. No problems. Then I started looking at virtual memory and anything else I could think of and happened to open up the disk quota tab under the local drive properties. Under "Show Quota Settings \ Quota Entries" I found that there were 3 NT service entries that were red-flagged and had 10gig space limitations. One of the entries was "NTAUTHORITY\SYSTEM" which was showing 9.99gig used out of a quota limit of 10gig. There were 2 other entries but I don't recall the specific nomenclature. However, all the NT entries were limited to 10gig, the now excluded network drive space limitation. I went in and removed the limitation on those 3 entry parameters and low and behold..... everything started working! I was able to install the software the user was having trouble with and was able to run all the updates from Windows Update that were causing low space error messages. It seems that the initial network login forced a local drive space limitation that ended up causing the issues. Whether by design or just something that I was unaware of, the network login forced the local user login to have a space limitation that only was enforced for those specific NT service entries. Everything else appeared fine and the user could download music, play videos, and do anything else that did not cause the system to write to a registry area such as doing an install. Once he tried something that did a write to a registry area, bang, no disk space errors. I'm glad I found it and I appreciate the help JB! It gave me the idea to look into the local disk quota service that finally led me to my conclusion and a happy end user! Kudos!

UPDATE - Had a chance to look at the laptop this afternoon. I confirmed that the user was excluded from the domain level disk quota, however, upon digging a little deeper into the local machine, I found that the local disk quota was causing an issue. It seems that the first network login, after upgrading from Win7 home to Win 7 Pro via the Anytime Upgrade, changed the local disk quota service and mimicked the domain level 10 gig limit. In Windows Explorer and in Disk Management, the local drive was showing a "normal" disk volume of 120gig used and 200gig free. However, upon trying to install an update or any software, an error would generate saying there was no disk space. The error was "error:80070070". I ran disk part, ran a check disk, scanned for malware/spyware/av and everything was giving me normal status. No problems. Then I started looking at virtual memory and anything else I could think of and happened to open up the disk quota tab under the local drive properties. Under "Show Quota Settings \ Quota Entries" I found that there were 3 NT service entries that were red-flagged and had 10gig space limitations. One of the entries was "NTAUTHORITY\SYSTEM" which was showing 9.99gig used out of a quota limit of 10gig. There were 2 other entries but I don't recall the specific nomenclature. However, all the NT entries were limited to 10gig, the now excluded network drive space limitation. I went in and removed the limitation on those 3 entry parameters and low and behold..... everything started working! I was able to install the software the user was having trouble with and was able to run all the updates from Windows Update that were causing low space error messages. It seems that the initial network login forced a local drive space limitation that ended up causing the issues. Whether by design or just something that I was unaware of, the network login forced the local user login to have a space limitation that only was enforced for those specific NT service entries. Everything else appeared fine and the user could download music, play videos, and do anything else that did not cause the system to write to a registry area such as doing an install. Once he tried something that did a write to a registry area, bang, no disk space errors. I'm glad I found it and I appreciate the help JB! It gave me the idea to look into the local disk quota service that finally led me to my conclusion and a happy end user! Kudos!

Glad to be able to help, thanks for the update!