Jump to content


anyweb

Root Admin
  • Posts

    9195
  • Joined

  • Last visited

  • Days Won

    367

Everything posted by anyweb

  1. Try granting the following permissions class called Package, and check the following Read, Modify, Delete and Distribute does that help ?
  2. i dont get it, can you give me remote access to this machine ? i assume its a Domain Controller ?????
  3. you must be doing Something wrong, and it must be related to how you are logging on to this server when i log on to my server i need to do so like this domain\user are you specifying domain\user ?
  4. its not connecting...
  5. ok trying now...
  6. i can do a remote session to your server if you want, just let me know
  7. it is not a normal user account, it is a service created during WDS intsallation. please uninstall WDS, reboot, remove the remoteinstall folder, reinstall wds and check again
  8. your problem is either a permissions problem or a mis configuration.. right click on your RemoteInstall folder in explorer and click on it's properties you should see an entry in there for WDSServer and it should have all rights if it doesn't then the WDS installation has failed and you can try adding them manually, or remove WDS, reboot, remove the remoteinstall folder, and reinstall WDS cheers anyweb
  9. if you are going to deploy Vista then you don't need mixed mode functionality
  10. after clicking on Member of, choose Object Types and make sure that Groups or Built-in security principals is selected, in your screenshot you've only selected Groups....
  11. the above tells you that you should have setup RIS first, otherwise you'll end up in native mode with no possibility of doing ris or legacy installs so maybe its time to uninstall WDS and start again by reading this WDS topic
  12. what type of user are you logged in as when attempting to do this ?
  13. what are you doing exactly in this screenshot, i need to know where in the guide you are exactly...
  14. try pointing it to d:\sources
  15. Domain Admins is present (it has to be) so you must be doing something wrong, try leaving it blank instead and click on check names and you need to do this as a user wit Domain Administrative permissions
  16. hi there its there too, you need to look harder, I'm using sql 2005 sp3 on my home SCCM lab (windows 2008 sp1 x64) don't install the 32 bit version of SQL, get the x64 bit version instead i've just checked technet and its there and
  17. take a look at this post then please
  18. bring up the properties of the Security group called SMS Admins, and click on the Member Of tab, Click Add and type Domain Admins thats it
  19. file not found means it cannot find a file to read or boot from verify that you have a boot image in windows deployment services if you do, is the WDS server running on the same pc as the DHCP server or a different one ?
  20. use Active Directory Users and Computers right click on Users, choose New etc
  21. you could probably write a small script to copy the contents manually to a folder and then once done install the application have you tried that ?
  22. hi and welcome you can create it by doing this
  23. ok in a production environment where you should have SCCM and AD on different servers do it like this make a global security group in Active directory Users and Computers and call it SMS Admins now, make two (or more) new Domain Users called SMSadmin and SMSread once done, log on to the SCCM server and startup Server Manager, Configuration, Local Users and Groups and select Groups double click on Administrators and add the SMS Admins Global Security Group as a member. (this gives the SMSadmin user local admin rights on the sccm server) in your lab do as follows: *if you have both SCCM and AD on the same server* create the two Domain Users in Active Directory Users and Computers called SMSadmin and SMSread create the SMS Admins Global Security Group and add the SMS Admins group as a member of Domain Admins.
  24. read this part http://www.windows-noob.com/forums/index.p...post&p=1442 that's where those accounts were configured
  25. you've pretty much answered your own question, and in this case you should probably install the os+drivers first, then after the os is installed send out the Intel Proset software by utilising the cache feaure
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.