JRyce
Members-
Posts
9 -
Joined
-
Last visited
Reputation
0 NeutralAbout JRyce

Personal Information
-
Biography
Have managed Netware 5.x networks for years, now moving in to MS AD world.
-
Occupation
IT Server/Network
-
Location
Kingston
-
I reached out to a couple counter parts at school boards near me. I was able to confirm that this was normal. The section I was talking about is supposed to show all computers that have the SCCM client installed.
-
I'm trying to get my head around our SCCM setup. I am coming in to this with most things already setup and I took a course on SCCM a while back. When I am looking at all the software updates (in the Software Library / Software Updates), and more exact, the "Software Update Groups", I see a lot of computers there that I didn't expect. For example, under a software update group named "Win 8 Updates" where I know there are only 80 some windows 8 computers, under "Statistics" (once I click on that group) I see a Total Asset Count of 7,284 computers. If I go to the Monitoring section and check that deployment for the update, I do see a smaller number (not the 7,284 computers). Is it normal to see pretty much all the computers in the system under the Software Library section? Just wondering if I am chasing something that isn't a problem. To me it seems to me that if we are pushing out updates only to our Windows 8 computers (by selecting that device group) it is still checking all the other computers and marking most of them as compliant because it doesn't need the updates. Every software update group we have all reports total asset count of being the same 7,284 computers. No matter how many computers are in the deployment. Any thoughts (if I didn't confuse everyone)? Thank you, James.
-
Thank you Nick. That did the trick!
-
Wondering if there is a setting that can make the user page, after logon, go directly to the users file menu. That is what we want the users to use by default. Thank you, James.
-
Hello all. Yet another Mandatory Profile question. I've been reading through a ton of the threads on here which have great info, but I am still struggling with getting Mandatory profiles done right. Client computers are mostly Windows XP with a few Windows 7 / Servers are Windows 2008 R2 Just when I think we are on the right track with an image we use in the Elementary side of things (the Man profile was a few Mb) we come across some of our High School Images with a bunch of Adobe products. Things like Dream Weaver CS4, Contribute CS4, Photoshop CS4, and so on. Now the profile we want to use to create the mandatory profile with has grown to over 30 Mb (if not more) just from answering the first time user registration type questions and turning off the welcome screen and such for these programs. I tried taking out all that stuff from Application Data folder (which is where all the Mb of data built up) but then the settings didn't stick for those programs. I read on blog that was linked to from a few threads here at this site ( Some Mandatory Profile Best Practices *** Updated April 16th 2010. « AppSense ) where he talks about just having ntuser.man on the server and nothing else. It seemed to work for our elementary image (just with a quick test), but not for the image using all these Adobe products. So now I thought I would ask if anyone had any pointers to make the Man profile smaller after making all the settings we want to set. We plan to lock the desktops and image down for the student machines with group policies (so we can enable not being able to make changes and such) but from my understanding of what I have read about Mandatory Profiles, they would still be a great help in our schools. The way I see it we have a few ways to do what we want as our end goal for student desk tops. 1/. Figure out how to make the Man profile smaller plus use Group Policies to tighten down security for student computers. 2/. If we can't get the Man profile small enough to be brought down over the network fast enough, copy the profile to the local drive (during the image creation), make sure it is read only on the drive, and point users to that (not sure if I like that idea for ease of updates and such, but saw that suggested here in a few threads). Plus use the Group Policies. 3/. Use just group policies to lock the desktop and the image down, and push out the registry settings for all the software settings required so the students wouldn't get prompted to register or other things when they log in for the first time on a computer. I can't recall if there are actually settings on the install of all these products that will suppress the prompts users get on first run (I don't normally do software installs anymore), but, I sure would like to sort out the Mandatory Profile thing and decide if that is the way we should go. Any suggestions would be great. Thank you, James.
-
Ben, I tried what Nick suggested with a copy and multiple applications (hap1/hap2/hap3, etc) and it worked like a charm.
-
This is fantastic! Just gave it a try and love the results. Thanks so much, James.
-
Thank you Nick. Yes that would work for us that way. Great app!
-
I think I know the answer to this already, but thought I would post the question anyway. I've installed HAP 7 and it looks really nice so far. If we were just going to set it up so that staff and students can access their own files in the home directory, one HAP site looks like it would work. But, what if I want to set up so the users can access a shared drive at each school? Do I need to set up a HAP page (site page) for every school so we can configure the shared area mapping? For the number of schools plus some departments, there would be way to many mappings if we tried to get every share on one site. I was trying to see if there was a way where you could use a next drive letter available (like in log in scripts) and only map the drives that a user would be a member of the groups. Setting up a number of HAP sites wouldn't be much of a problem as once the settings are done (for just using the file access part), I don't see it changing much. Nice job on this program by the way. Thank you, James.
