![]() ![]() You may wish to take a quick look at what services you can stop & remove (see below), however. ![]() This will fit onto a 256Mb partition with no problems (n fact, when you reduce the partition size from 512Mb to 256Mb, you will gain a few Mb more space by going from 8k clusters to 4kb clusters). Your system should now be approx 218Mb (mine was 228,827,136 bytes) on a 512Mb FAT partition. The problem is, you won't know for sure until AFTER you have run sysprep, cloned the image to a 'real' processing 'node' and actually started to run SETI inf file is being 'used' for anything by checking to see if a matching. A 'search' of the whole C: drive reveals 11 more *.pnf files hiding in the c:\windows\dell sub-folders (92,432 bytes) that can also goĪ quick note re. I guess nLite leaves them behind to save time 'in case' you want to re-process the build. inf is used (typically during installation). They can still be deleted by booting from a DOS floppy, however sys-prep should clear them anywayĬ:\windows\inf\*.pnf, 73 files (approx 4.7Mb). log files are held 'open' when windows is running (3, 4, PASSWD, default, SAM, SECURITY, Software, System). Since you are never going to uninstall and re-install sp2, it's not neededĬ:\windows\ *.log 31 files (1.6Mb), *.tmp 4 files (2.1 Mb), *.txt 4 files (0.3 Mb) At least 13 of the. CatRoot relates to the base system install, however CatRoot2 appears to be used only during Service Pack 2 install. Consisting of 3 subfolders, \templates, 5 Files (719,214 bytes), \logs, 3 File (105,842 bytes), \Database, 1 file (3,153,920 bytes) for a total of 9 files, 3,978,976 bytes Templates for changing Security settings and log files of changesĬ:\WINDOWS\WinSxS\Manifests\*.cat (12 files, 88,203 bytes) Ĭ:\WINDOWS\system32\CatRoot2\*.*, 13 Files (2,378,533 bytes), & both sub-folders 2 Files, (3,153,928 bytes), total 6.5Mb. Registry back-up (copy of the Registry at time of install or last MS Back-up)Ĭ:\WINDOWS\security\ complete. cat files ?Ĭ:\WINDOWS\Driver Cache\i386\*.*, 2 files (5,088,098 bytes) The 2 files, sp2.cab & driver.cab are included so you don't have to supply the Windows Install CD when 'rolling back' a driver (or installing 'new' Hardware)Ĭ:\WINDOWS\repair\*.*, 8 Files (4,067,838 bytes). files that can be deleted ?Ĭ:\dell\ (7 files, 242,720 bytes) = the whole folder can goĬ:\windows\system32\dllcache\*.*, 20 files (6,297,266 bytes) = the whole folder can go This folder should have been removed when Windows File Protection was disabled, however somehow nLite leaves it behind full of. Finally you remove the hard disk and go onto the next node. You then reduce the 512Mb partition to 256Mb and CLONE it across to the 256Mb device. You add a temp C: hard disk formatted to 512Mb FAT & install the 230Mb nLite onto the hard disk. Say you are using 256Mb DOM / CF / USB on your nodes. There is no point in reducing the install and Sysprep'ing it UNLESS you need to install direct onto other 256Mb partitions After install you can CLONE it down to a 256Mb partition The 230Mb nLite will INSTALL onto a 512Mb partition. Many (WebClient, ICS, Wireless Zero Config, Bluetooth & IR device support) are included simply because I specified Ethernet support and these files & services 'came along for the ride', some (IPSEC, NT LM) are included 'just in case' your computer is ever connected to a Corporate DOMAIN, whilst others (HID, Server, Windows Installer) seem to have been included as part of the 'basic functionality'. However this 'minimum' build still contains numerous tmp, log, cached (and some other duplicated) files plus 29 services, of which only 19 are normally running. In fact, the source snapshot setting for an additional disk is disregarded.The minimum installed nLite system is approx 230Mb. Instance template with the exception of the instance name and zone. When you use an instance template to start a VM instance, the defaultīehavior is to create a VM instance exactly as described in the The documentation Creating a VM instance from an instance template with overrides claims source-instance-template instance-template-1 \īehaves in a similar way: it creates a VM instance with a blank additional disk instead of a disk from a snapshot. ![]() The gcloud command $ gcloud compute instances create vm-gcloud-from-instance-template-1 \ ![]() create-disk=mode=rw,auto-delete=yes,size=10,type=pd-standard,device-name=persistent-disk-1 If you looked at the gcloud command line proposed by the Cloud Console when you create a VM instance from an instance template, you would see that instead of a command with an expected option -source-instance-template it composes a plain command gcloud compute instances create that disregards the source snapshot setting: $ gcloud beta compute -project=my-project instances create vm-from-instance-template \ ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |