Jump to content

sacrej

Members
  • Posts

    120
  • Joined

  • Last visited

Reputation

22 Excellent

1 Follower

About sacrej

Personal Information

  • Occupation
    IT Technician
  • Interests
    computers, drums, guitar, photography and photo manipulation of a surrealistic nature, Heavy Metal!!
  • Location
    Ryde

Employer (optional)

  • Company Represented
    Ryde High School
  1. set to disabled in gpo, tried to change to unconfigured - no joy :/
  2. Oh those options, yes I have those - however they are all grayed out with the bottom option selected (Enforce NLA) not sure how to 'un-gray' them :/ I am logged in as a domain admin, local admin has the same issue.
  3. unfortunately this doesn't seem to be an option on R2 (that i can see)
  4. please read my previous posts as I have already provided this information. Enforce NLA - greyed out due to Negotiate selected making it 'optional'
  5. we are on 1.3 and just tried to get it working on win 7 to not much avail - it works for domain admins, on x64 and x32 but not regular users staff/students i'm actually trying to get it working in APP-V captured on a winxp machine, which works as above, the errors I get are: Error: JZ006: Caught IOException.java.net.SocketException: Create Now obviously SME DOES work on Win7 as i've had it running as a DA, so i'm thinking it must be a permissions issue The mapped network drive (L:) is correct and users have the correct permissions on it (it works on XP previously) We're using Sybase on a 2003 server, though I wasn't around when all of this was set up, its a matter of urgency that we get this sorted as soon as! well, they say its urgent anyway!
  6. does anyone know if there is a way to force disable NLA in 2008r2sp1, as I think that this would solve all of our issues. all the options under remote connections are greyed out and the options in TS dont seem to do anything either.
  7. also, 32bit versions of programs can only utilize a certain amount of memory 2-3gigs tops I think, for example Photoshop 64bit will utilize a lot more if given access to it. memory footprints are generally a bit larger for 64bit apps, so really 4 gig would be a minimum, I have six in my work machine, but my home has 4gig and I run stuff like cinema 4d x64 and photoshop x64 without any issues, although on big jobs and processes the more memory the better. for photo & video editing and anything requiring rendering (CAD, CG etc), in an ideal world I would give them minimum of 8gig plus x64... but that's wishful thinking. darn those budgets! on our 2gig curric machines we use x32 but for staff laptops we're thinking of rolling out x64.
  8. re-read my original post, but to add security layer - negotiate Encryption Level - Client Compatible Cert - (Domain CA provided) Enforce NLA - greyed out due to Negotiate selected making it 'optional'
  9. WYSE S10 with WTOS 5.3.0.09 machines pick up dhcp option to pick up WNOS.ini answer file from ftp server (this works) answer file tells them to run rdp connection to server 'studentRD; 172.16.45.103' this brings up an rdp connection on full screen normally, now we just get a short message saying "Connection "studentrd": connection failed. on the terminal event log I get loads of invalid statement:"random characters" after the 'Accessing system profile' event, may I reiterate that this event log is on the CLIENT the server doesnt really provide any information in the event log, before we removed the service pack it was showing some error messages specifically stating those machine names, but they seem to have disappeared now. i'm tempted to reinstall the service pack to see if they start showing up again
  10. They are thin terminals, there is no downloadable client, desktop machines connect fine. we uninstalled the service pack, but they still cant connect. it's the only thing we have changed on that server in a very long time! if I change the wnos.ini answer file to point to a different terminal server (2003) that works okay...but thats a staff rd server, the weird thing is that this all worked prior to the sp. gah
  11. we also use the GIMP instead of photoshop.
  12. we have office 2010 and libre office on our build (was my decision to slip it into our new win7 build at the last minute) not much usage but for the people that know what it is, i'm sure they're greatful. chosen over open office, due to the lack of oracle-ness
  13. If you're rebuilding existing machines, you could always run litetouch.vbs from scripts under deploymentshare$ (using MDT) we push it to all machines we want to image using abtutor, go round fill in the details and leave it to run, no more user interaction required, this is with a precaptured windows 7build. I want to try and get ZTI/UDI working using SCCM2007 but its pretty heavy work when there is only 2 of us and a whole school to support. :/ seriously though, using the vbs meant we could set them off at the end of the day and then just go home, before we would have to wait for them to finish and fill in the existing details, or go round and f12 at boot for pxe, this process bypasses PXE completely which is awesome, and I believe you can use it to capture/sysprep machines too. it adds the winPE boot image to the system bootloader so when the system restarts it comes up automatically.
  14. hey, we came from novell + Zenworks, migrated to 2003 + zenworks 6 years ago and then last year binned zenworks and moved to 2008r2, plus hyper-v/scvmm and App-v instead of zenworks. we also had deep freeze before and it sounds bad, but we didnt put AV on curric machines as it slowed them right down (old p4's, 256mb ram xp) we now have new workstations and win7 enterprise accross the board and have binned deep freeze as it was such a pain, also not patch management/SCCM friendly. we lock the machines right down via GPO and delete local profiles periodically and we have AV locally now. much better IMO.
  15. None of our clients have been able to connect since applying the SP, so we're going to have to return to roll back, what we've found is that it wont let us turn off Network level authentication, if anyone can suggest a way to work around this then I would be very appreciative. We no longer have a support contract and I couldnt say what firmware they are on, but they did work with R2 previously with security set to negotiate on the server.
×
×
  • Create New...