Jump to content

Asin

Member
  • Posts

    181
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    Canada

About Asin

Asin's Achievements

0

Reputation

  1. So if I have my RIS Server on a domain in which the domain controller is its own DNS Server, one that is different from the one assigned by DHCP, the FQDN won't work will it? Just to be clear, Option 67 needs to be set to '\RemoteInstall\Setup\English\Images\WINPE\i386\templates\STARTROM.COM' in this case right?
  2. So I found this Microsoft Knowledge Base article about deploying WinPE images. http://support.microsoft.com/kb/304992 It mentions that you can deploy ISO images, but the creation process makes it sound like you can't just any WinPE ISO since it needs the i386\system32 folder. There's a WinPE ISO inside this customized ISO, which is where some of the files the articles asks for are. I copy those after I mount the ISO in the ISO. This doesn't appear to work though. I run into the "PXE-E55: proxyDHCP service did not reply to request on port 4011." error. I have Scope Option 66 set to the IP of the RIS Server and Scope Option 67 set to "RemoteInstall\Setup\English\Images\WINPE". I don't know if this is right since it's my first time setting up RIS. I've tried many variations on Option 67, including not using it. Does anyone see something that I'm doing wrong? Also, can I use this customized ISO which has a different folder structure? Any help is greatly appreciated.
  3. Do you see any other QuickLaunch icons? It may simply be set to now show right now. When you're checking, are you sure that you're in the Administrator account?
  4. Thank you. That worked nicely. I don't think that I've ever needed any escape characters before.
  5. In a nutshell, this is what's in my .REG file: Windows Registry Editor Version 5.00 [HKEY_USERS\.DEFAULT\Control Panel\Desktop] "Wallpaper"="C:\WINDOWS\Web\Wallpaper\MyWallpaper.bmp" I'm trying to change the default background for the login screen. The file copies to this location perfectly. I've tried double-clicking on the .REG file and using a silent install from the command line using REGEDIT /S. I can't figure out why this won't change (or even create after deleting the original) the correct entry in the key listed. There are spaces a hyphen in the full path to the .REG file, but that's never stopped me before. In fact, I just copy and pasted this from anther one that works since I was too lazy to type out the first line. I vaguely remember something similar to this happening but I don't remember why. Any help is greatly appreciated.
  6. Here's a strange one. When a user double-clicks on a mail message, the text body is completely blank. If that user clicks on Reply or Forward, you can see the message in the idented text for reply or forward. The From and To fields are all legitimate emplyees and the Subject line is not blank. This has happened to one user with Outlook 2003 with random messages and another user on Outlook 2000 with messages that have attachments. There may or may not be a correlation. Outlook Web Access shows the same thing which suggests Exchange Server-side issues. What could be causing this?
  7. I haven't had a chance to play around with this and I think that it would be quicker just to ask. If I use the command net localgroup /add Administrators DOMAIN\Admins Will this use the currently logged in user's credentials to authenticate? That is, if I am logged into my account that has access to ActiveDirectory in several Organizational Units and local administrative privileges on the local machine, I can clearly perform this command without any trouble. If I have just local administrative privileges but no access to ActiveDirectory or any Domain administration access whatsoever, am I still able to run this command and have the result that I want? I have a feeling that the Check Name using the GUI would fail, but would this work from the command line? This theoretical user would be logged into the domain under a regular domain user account.
  8. Sorry, when I said more responsive, I meant actually working. XCOPY tends to die on me when I try to copy all relative files (i.e. ".\*.*") from an Everyone Full Control network share. When I say die, I mean that nothing is copied. It keeps saying "0 file(s) copied". I think that I got into a bit of this above. I don't have a full listing for everyone's possibly network drives upon logon. As a result, I'm just trying to do this so that anyone can use it. This looks like it's exactly what I need. I'm not too familiar with the FOR loop command nor conditionals in DOS. What exactly is the exit condition in this code? I know what it does since you typed that up in response to what I'm asking for. But can you or somebody else just explain it a little more?
  9. I'm trying to set up a script for others to use to install programs. I'm not fully aware of all that happens in this IT Department just yet since I've only been working here for a month. There may be reserved drive letters or random changes that I have no control over nor know about in the future. I'm only going to be around for 3 more months so I wanted to make something that is somewhat universal. The name of the computer isn't going to change after I leave. In my VMware tests, scripts seem a little more responsive if you use a constant drive letter as opposed to the network path.
  10. I'm trying to figure out how to get the next available drive letter. I know that if I use the command: net use * \\computername\sharename * it will map to the next available drive letter. In this case, Y:\. How do know that if I'm trying to automate a batch script though? Any help is greatly appreciated.
  11. Wait, I got it. The virtual network drivers that were installed utilize Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks. I've since uncheck those for both virutal adapters and things seem to be moving smoothly again.
  12. Here's the situation: I don't have Ghost Server or Ghosting software other than bootdisks with me. The ghost.exe version on the bootdisk is 8.0, so that's what I'm assuming they used to make the disk. I'm trying to load an image on the target computer from the source using a network share. I can get through the bootdisk options and when I try to use the command: net use x: \\COMPUTER\SHARENAME$ to map the share with the image, it fails on me and says that it can't find the network path with an Error 52. However, this works with other computers just fine. Mapping the share I mean. The only difference that could possibly affect this is VMware Workstation which installs a virtual network driver on the source machine. I've since uninstalled VMware and for some reason, the bootdisk now works on the target machine. Any ideas why this network driver is causing a conflict? Any help is greatly appreciated.
  13. Script the installation using a batch file. Just have everything exactly as shown: ECHO Please unplug the ethernet cable before continuing. PAUSE <Code for installation. i.e. %SYSTEMROOT%\Applications\Installer.exe> Well, not exactly. Change the last line to whatever you use to install the program. Otherwise, put the path to the executable file.
  14. The local Administrator account always exists and this person would always have access to it. For some reason, the IT Manager has decided that roaming Administrator privileges using the domain user account for that person should not be granted despite the fact that that person already knows the local Administrator password for all the computers. Thank you Doc Symbiosis. I wasn't aware that you could use the command that way. The online documentation from Microsoft wasn't all too helpful. The examples didn't show anything like that. Any use of the /add switch always referenced created a new local group on the local machine.
  15. I figured that this fits in the Unattended section of the forums more so than the non-Unattended section since I plan on using login scripts to carry out my goal so that it will be quick and painless. My goal is to create a group with appropriate permissions in a domain environment and add this group (call it DOMAIN\Admins) to the local Administrators group on the local machine. Basically, this gives anyone in DOMAIN\Admins roaming local administrative privileges on the domain. In addition, I would like to add the user that uses that computer into the local Administrators group. But that's pretty much the same as above. In the end, what I want to do is allow for users A, B, and C to all have the ability to create and delete computer accounts in the domain, but to restrict user C from having roaming local administrative capabilities. That is, if user C does not log in to his computer, he will not have administrative privileges. I am aware of the implications of giving users full administrative privileges on their machines, but that is not what I am asking here. There are other measures in place to prevent anything that should not be allowed already. The commands NET LOCALGROUP and NET GROUP are confusing me. I do not even know if they are useful for what I am trying to do. At the moment, the local Administrators group does not have DOMAIN\Admins. This is what I plan on aiming for first through a login script making the transition very quick. Any help is greatly appreciated.


×
×
  • Create New...