Fonts install
How do I perform a snapshot w.o. executing a program. All I wanna do is add a file and reg entry (font).
I use Wise. Thanks
I use Wise. Thanks
0 Comments
[ + ] Show comments
Answers (15)
Please log in to answer
Posted by:
sam386
15 years ago
Thanks for all the tips guys but what I am dealing with is the damn Fonts folder. When I do a copy it shows 0bytes on each font file that I pkg. My next question is how can I delete certain fonts ex. nam*.ttf and then call a VB script that re-registers new fonts? I have the script and I have the fonts I need. I need to do it in that order so I can run it as a GPO dist. Is it a module? Oh yeah, I wanna pkg this as an MSI.
Thx
Thx
Posted by:
anonymous_9363
15 years ago
I don't understand what's so hard here.
- Start a capture
- Remove whatever fonts you no longer need.
- Drop your new fonts into the fonts folder
- Restart your VM/VPC/VBox
- Finalise the capture
You *may* need to add detail to the RemoveRegistry table to ensure that registry entries relevant to the deleted font files are removed as well, as deleting the files (even using Control Panel) does NOT necessarily remove this data.
- Start a capture
- Remove whatever fonts you no longer need.
- Drop your new fonts into the fonts folder
- Restart your VM/VPC/VBox
- Finalise the capture
You *may* need to add detail to the RemoveRegistry table to ensure that registry entries relevant to the deleted font files are removed as well, as deleting the files (even using Control Panel) does NOT necessarily remove this data.
Posted by:
AngelD
15 years ago
Posted by:
sam386
15 years ago
ok guys I think I have this in the bag. an msi that runs under the user shell. now my question is if I run it by calling the msi using a startup script GPO, is that the same as a user based assigned software deployment?
and if I do a startup script i dont want the install to continuously loop so will the below work via GPO?
Thank You
@echo off
IF EXIST "C:\FILENAME.TXT" THEN GOTO END ELSE GOTO INSTALL
:INSTALL
MSINAME.MSI /qn
OUTPUT > C:\FILENAME.TXT
:END
EXIT
and if I do a startup script i dont want the install to continuously loop so will the below work via GPO?
Thank You
@echo off
IF EXIST "C:\FILENAME.TXT" THEN GOTO END ELSE GOTO INSTALL
:INSTALL
MSINAME.MSI /qn
OUTPUT > C:\FILENAME.TXT
:END
EXIT
Posted by:
sam386
15 years ago
Posted by:
aogilmor
15 years ago
Posted by:
anonymous_9363
15 years ago
Posted by:
sam386
15 years ago
Yes. We can use the MSI created using your recommendation in post 8 when we are logged on to the pc. What isn't working is attaching the msi as a computer or user assigned sw pkg via GPO. I should also add that I'm no pkg or GPO expert and don't mean to come across as an ass but there is NOTHING out there on this issue (deploy replacing fonts) with new versions. Like I said before i think it has to do with the Windows File Protection built into Windows. We can definately fix it using the MSI but it sure would be nice to deploy the solution. If someone can mock it up (replace a font) and get it to work I would love to know how you did it.
Posted by:
anonymous_9363
15 years ago
AAAAaaaaaaaaahhhhhhhhhhh....you're REPLACING fonts, not installing new ones! First, WFP doesn't apply to fonts, so forget that. I suspect the problem is how the Windows Installer engine handles files which don't contain binary version information. In summary, if a file in an MSI is older than (or the has the same date/time-stamp as) an existing file, it won't be installed. THIS is what I suspect is happening here.
- Clear out %SystemRoot%\TEMP
- Enable the MSI Logging policy on a target workstation (no need to reboot for this one)
- Run GPUPDATE on the w/s.
- In %SystemRoot%\TEMP there will be a selection of files names 'MSI[random alpha-numeric].LOG. Use the DOS FIND command to locate the one you're interested in. Easiest route is to use the ProductCode:
.....FIND /I /C [your MSI's product code] MSI*>LOG
- Open the log file and seek out the FileCopy entries. I suspect you'll see that the date/time-stamps mean that the existing files are left in place.
- Clear out %SystemRoot%\TEMP
- Enable the MSI Logging policy on a target workstation (no need to reboot for this one)
- Run GPUPDATE on the w/s.
- In %SystemRoot%\TEMP there will be a selection of files names 'MSI[random alpha-numeric].LOG. Use the DOS FIND command to locate the one you're interested in. Easiest route is to use the ProductCode:
.....FIND /I /C [your MSI's product code] MSI*>LOG
- Open the log file and seek out the FileCopy entries. I suspect you'll see that the date/time-stamps mean that the existing files are left in place.
Posted by:
aogilmor
15 years ago
Posted by:
anonymous_9363
15 years ago
Posted by:
aogilmor
15 years ago
ORIGINAL: VBScab
Using SUC seems an incredibly long-winded way to add a file and some registry entries in WPS. Why not simply add the file in the 'Create new MSI' UI and then import the .REG?
I didn't read the entire post...thinking/ guessing he probably doesn't know exactly what changes his configuration actions will make, e.g. launching the app instead of setup. I've used it in this way, as a kind of discovery tool.
If he's installing files and making reg entries directly, true, just add them in wise for windows intstaller, no need for snapshot.
Posted by:
revizor
15 years ago
Posted by:
anonymous_9363
15 years ago
Posted by:
InterneToughGuy
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.