Jump to content

morganw

Members
 View Profile  See their activity

  • Posts

    827

  • Joined

  • Last visited

 Content Type 

Everything posted by morganw

  1. morganw
    Any chance they could use remote desktop services instead of a full PC?
  2. morganw
    You could put a storage node into each remote site so the images don't travel across the slow link. You could then manually transfer new image to it from a drive or let the replicator service take it's time.
  3. morganw
    I haven't had a play with Windows 7 and FOG yet but i'm pretty sure that if you have set the OS type to 'Windows 7' the imaging and restore processes will be looking to work with two partitions not one. This might be why you are getting the error. You could try using the default two partitions, or set the OS type to 'Vista' to work with a single partition. Also make sure that you run Fogprep as an administrator as it's functionailty is blocked by UAC.
  4. morganw
    I use 2008 R2 with all XP clients. I've got not scripts at all now, pretty much everything is done with group policy preferences and I don't get many problems. As previously stated, it will log any processing problems so you should be able to see in the event viewer where the problem is. Might be worth testing on a different account as well as once I had an account which refused to process GPP stuff without errors, just deleted it and remade it and no problems since.
  5. morganw

    Robocopy Script

    morganw replied to harrimann's topic in Scripts

    If using robocopy you'll probably want to use the archive bit to differentiate between modifed and unmodified files. /A : Copy only files with the Archive attribute set. /M : like /A, but remove Archive attribute from source files
  6. morganw
    Can't remember where I got this, and I modifed it slightly by commenting some bits out as we use it to clear a temp folder, but I think this the type of thing that you are looking for: Set fso=CreateObject("Scripting.FileSystemObject") CleanPath="E:\Network Temp\" For Each file In fso.GetFolder(CleanPath).Files file.attributes = file.attributes And Not 1 file.delete Next Set fso = CreateObject("Scripting.FileSystemObject") Set oFolder = fso.GetFolder("E:\Network Temp\") arrFolders = Array() For Each oFolder In oFolder.SubFolders ' Note : Only use *lowercase* letters in the folder names below: 'If Not LCase(oFolder.Name) = "foldera" _ 'And Not LCase(oFolder.Name) = "folderb" _ 'And Not LCase(oFolder.Name) = "folderc" Then intCount = UBound(arrFolders) + 1 ReDim Preserve arrFolders(intCount) arrFolders(intCount) = oFolder.Path 'End If Next For n = 0 To UBound(arrFolders) fso.DeleteFolder arrFolders(n), True Next Set objFSO = CreateObject("Scripting.FileSystemObject") Set objFile = objFSO.CreateTextFile("E:\Network Temp\The contents of this drive will be deleted every night") Out of interest why aren't you allowed to use a program to acheive this? Technically the script interpreter is a program you just don't see any evidence of it running unless you get an error.
  7. morganw
    Am I the only one who thinks that it's simpler to have more GPOs? I find it more straight forward to have GPO do a function, or group of functions, name the GPO after what it does prefixing them to differentiate between application settings, user settings, computer settings etc. There might be an overhead on replication and GPO application but it means that it's easier to track changes via the modification dates, easier to find something when i've forgotten where I made the change, and if I were hit by a bus my replacement could look at the GPO names and structures and get an instant idea about how everything is actually setup.
  8. morganw
    Gutted, I bought mine from them at the end of November.
  9. morganw
    You can re-run the installer on the same hardware with no problems, not sure what would happen re-running it on different hardware, I guess it would be ok. If I were you I would set it up in a VM so it's portable, copying the images from the old server, possibly the database if you would have to re-add a lot of hosts. Having it in a VM also means you take snapshots before running OS or FOG updates in the future and rollback in case of problems. If the VM can't cope with the load then set up a physical storage node with the VM set as the master node - you'll get the reliabilty of the the main system being virtual with the performance of the physical storage node. If the storage node dies just make another as it doesn't carry anything that isn't on the main server.
  10. morganw
    Looks interesting. Can it automate the setting of workstation names and join the domain?
  11. morganw
    I'm sure when I set the DHCP options for FOG on a server 2003 system I didn't need to deactivate a scope or anything to put the changes in.
  12. morganw
    Rather than a new domain and using using different partitions, what about using a standalone terminal server with all of your restictions applied and then just connect into that with a PXE boot system like thinstation or use a web access gateway.
  13. morganw
    You could use cacls in a for loop in a batch script, or you can do something similar in powershell with get-acl and set-acl cmdlets. It is more work in the short term but you can customise your scripts to also do other things like populate other fields in AD, create the shares on user folders, put users into the correct security groups etc. Could save you time in the long run.
  14. morganw
    Probably a switch problem if they are all the same model. I occasionally get a glitchy transfer but it's usally about 1 out of every 150 or so imaging tasks that needs to be redone. If they are different models of PC and you get the issue again then you could try a different kernel and see what happens. Also watch out for recovery partitions on PCs which normally need to be removed before imaging will work properly.
  15. morganw
    Do you mean you are getting an error when imaging a second PC (and a first one is fine) or do you get an error while trying to image two PCs at once?
  16. morganw
    Would that be two unicasts or one multicast with two clients?
  17. morganw
    I think you need to set Always wait for the network at computer startup and logon in the local policy of the machine that you used to make your sysprep image. If you define this setting via Group Policy it's too late for it to make a difference on the first boot. The other thing that I've found to affect this is using a sysprep image that was created before a daylight savings change. This will also not install not software on the first boot as the timezone doesn't match the domain. So everytime the clocks change you have to redo your image to keep installing software on the first boot.
  18. morganw
    Working with Active Directory Users and Computers
  19. morganw
    Wouldn't you just use ADUC to connect to all your domain controllers and check that the computer objects are there?
  20. morganw
    It's in the tar file that you download and you run it on a windows computer to convert your password to an encrypyted one. There are instructions here along with notes on making the encyption more secure.
  21. morganw
    You can check the log file (normally C:\fog.log) is see what is going on. If it doesn't attempt to join then check that you've got the Active Directory settings and the 'join' checkbox set for the host, if it is attempting and failing it's usually a bug causing the format of the username to be wrong or the account used to join the domain doesn't have permission to create or modify computer objects. Most of the issues are covered here.
  22. morganw
    If you've got the FOG service installed as part of the image then it will rename on the first boot and join the domain on the second. Yes it's easier to let FOG handle all of the hostnames rather than manually try to set them. If you need to rename a workstation just change it's name in FOG and then create a new deployment task, overkill just to change a name but doesn't require manual fiddling.
  23. morganw
    If you want to switch kernels you can do this at a host level by setting 'Host Kernel:' to "fog/kernel/KernelName". The quick image option will always use the default kernel though so potentially you might have to actually setup a deployment task in the web interface for some computers which will use the 'Host Kernel' setting. I find it works best to use an older kernel as the default, then make per host exceptions to a newer one, but that's probably as most of our computers are a little old.
  24. morganw
    At the moment the FOG service doesn't work 100% with Windows 7, it is apparently getting update within the next couple of releases to add better support for this OS. In it's current state with the extra features it offers using the service I would say it's the best way to deploy Windows XP. If you are looking to go to Windows 7 in a couple of months it will do the imaging, but you'll have to sort getting a universal image together that will work on all your hardware - something like this may be easier to create and update with WDS / MDT2010. Personally I've ended up using using a lot of extra features in FOG like printer managment, screen resolution changing, inventory, and using snapins it does all of our software installation. Moving from FOG means replacing all of this functionality and somewhat de-centralising the management tools so even if Windows 7 with FOG is more work in terms of the actual imaging it might be worth sticking with it. You could try both at once and see which fits best, if you run DHCP client groups and enter the MAC addresses of some PCs you can set PXE boot options to force a boot from the FOG server rather than WDS.
  25. morganw
    Souns like you are running behind a proxy but haven't entered the proxy details into the FOG settings. Once this is done that page show a range of kernels which you click to download.
×
×
  • Create New...