Jump to content

chilifrei64

Member
  • Posts

    996
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by chilifrei64

  1. have you tried upgrading to the latest version of java?
  2. really you could use any... but since a workstation is scaled down alot compared to a Server you would want to use the mose scaled down version of Server OS which would be Standard.. unless you want to use your workstation as a web server or a massive SQL Server or have more than like 5 processors...
  3. I wouldnt say it is Norton... i dont run any norton utilities on my PC and I too have seen this message... I started looking up online about what this means and i guess from what i have found it is just general debug lines in the program code that is mainly used during testing. I mainly found that when people referenced that string it was regarding a driver programing. Obviously you "arent supposed to see" it but we do... Basically what i gathered is it is just sloppy programming. Check and see if the manufacturer has an updated driver for your card and that you arent running beta versions of anything on your computer..
  4. So far... So correct.. Office 2003 and Adobe CS can run as standard users. QuickBooks and Mas200 is another story What I have done with Quickbooks and MAS90 at one of my old clients was set specific user rights assignments and file permissions using Goup Policy. This is somewhat of a tedious process(atleast for quickbooks) but if you download a registry monitor and a file monitor you will see what files/registry keys it is trying to access and it wont have the correct user rights. Modify the GP accordingly and try to run it again and search for another error. Once done with setting the permissions apply it only to the users needing it (ie. Quickbooks_Users group)..<-You make this group yourself MAS90 was essentially just giving permissions to the registry key under LOCAL_Machine that MAS90 uses. this took care of most of my problems. I would assume MAS200 would be similar If you are OK with just assigning Power User permissions to the users then assign this permission first and use the above process to determine the rest of the problems I hope this helps, I spend alot of time makeing applications work as standard users.. this process was tough for me for a while. I am on about a week (actually prolly only 8 hours total)for a current problem software that requires admin rights. Ill tell ya though.. it is worth the time now to figure it out, none of my users have permisssions to break anything. I love it. EDIT: Link to registry monitor and file monitor Registry Monitor: http://www.sysinternals.com/Utilities/Regmon.html File Monitor: http://www.sysinternals.com/Utilities/Diskmon.html
  5. this all depends on the software they are using.............................
  6. Open your group policy manager go to User configuration-> Administrative Templates-> Windows components-> Windows Explorer Enable "Hide these specivied drives in My Computer" and "Prevent Access to drives from My Computer" and configure accordingly For Folder Permissions.. this is GPO too Computer Configuration -> Windows Settings -> Security Settings -> File System Set your permissions accordingly here.
  7. yeah somebody just posted this like 10 days ago http://www.msfn.org/board/index.php?showtopic=51694
  8. you gotta register but this is the link http://www.microsoft.com/windowsserver2003...al/privacy.mspx
  9. boot to the recovery console from your windows installation CD or boot into BartPE and run chkdsk This is not working for you because the volume you are running chkdsk is the system volume and it needs to unmount it before it can fix the errors.. it cant unmount while it is running..
  10. yeah it is probably the virus... the easiest way to tell if your system32 folder is missing is to reboot... if windows comes back up then it is still there.. if it doesnt.. then it isnt there
  11. download the group policy management console and run Group policy results and let us know what it says.. it should tell you what the error is.
  12. it will work in a live enviroment.
  13. Are the users and computers in different OU's or the Same (should be different)? Did you apply any security filtering or WMI Filtering? Did you download the group policy management console for 2k3 server? Did you apply it to Authenticated Users? Did you run a gpupdate /force on the machine? Was the policy assigned to an OU or a site? Also please explain how you set it up IE.. Added users to Management OU Applied group policy to Management OU and security filtering for Authenticated users..blah blah blah you know.
  14. what you are going to want to do is log in to the computer using the guest account because local policies dont affect it... Run gpedit.msc as administrator.. make your changes. then remove permissions for the administrator on that folder.... If you already had an administrator profile created, delete it as it will probably already be affected. This method will work for User Settings ONLY.. anything applied to machine settings will still affect the administrator.
  15. search through your router settings to see if it is running DHCP.... If it is... then dont worry about this part.. if it is not.. let me know
  16. Alright. On your computer, make sure you have your wireless network connection as follows "SSID Name" Properties Association tab: Make sure the SSID is correct.. this means caps and all. Network authentication should be open and wep should be disabled. Authentication Tab: make sure none of these are selected. Wireless network connection properties Make sure "Use windows to configure my wireless settings" IS checked Make sure your ssid is the top one Select the advanced button and select "Any available network" Also, make sure your router is handing out IP Addresses.. if it is not then staticly configure one on your computer based on the settings from your router (IE. Router IP 192.168.0.1 SM 255.255.255.0.... Computer 192.168.0.2 SM 255.255.255.0 DG 192.168.0.1
  17. Try this.. it was a post about 10 days ago http://www.msfn.org/board/index.php?showtopic=51694 From my experience.. this only works to remove the OS check in MSI installers
  18. Well what I would do is get them a router and have that act as their firewall then just dont use the local ones.
  19. either one.. whichever one you can connect to it with.
  20. Check this out.. maybe is it of some help http://www.jrbsoftware.com/09enhancements/enhancements.htm Look down where it says Jrbimprt then it is abotu 13 bullet points down from there.
  21. I recent forum post under networking and security here has a quick how to that seems to be working for everybody http://www.msfn.org/board/index.php?showtopic=49589 or if you want REAL comprehensive you can check this out http://www.microsoft.com/technet/prodtechn...g/rmotevpn.mspx
  22. Login to your router using the web interface and start fishing through there for the settings. The address to the router will be your default gateway address. To find out your default gateway go to start-> run -> cmd type ipconfig /all This will tell you if you are set to autoconfigure (yes or no) and what your default gateway is. Once in the router.. search for the settings i mentioned above What version of the router are you using and what firmware version is it running. Most Netgears have an update firmware page on them where you can update the firmware.
  23. Have you checked the event log on the workstations you are applying this to. Either 1 you get a cannot fine ......loginscript.vbs which means you have hte wrong path set or you get a general error in the security log stating bad username or password/computer not trusted or you dont see anything which means that either the script is running perfectly with no problems(not the case) or it is not applied correctly using group policy. Did you do any security filtering on this GPO? What Version GPO are you using(2000/2003/Local) when you are setting the path to the login script... are you using the UNC path to the script?
  24. What was your solution?
  25. yeah.. best bet is to use a VNC type software.. you cannot RDP into a windows 2000 box unless it is a windows 2000 SERVER OS
×
×
  • Create New...