SnapinPacks - Revision history

Wayne-workman.28155 at 17:20, 28 October 2016

2016-10-28T17:20:15Z

Wayne-workman.28155: /* SnapinPacks are Compressed */

2016-10-21T02:26:44Z

‎SnapinPacks are Compressed

Wayne-workman.28155: /* SnapinPacks are Compressed */

2016-10-21T02:25:23Z

‎SnapinPacks are Compressed

Wayne-workman.28155: /* Snapins Run as SYSTEM or root */

2016-10-21T02:17:27Z

‎Snapins Run as SYSTEM or root

Wayne-workman.28155: /* Snapins Are Silent */

2016-10-21T02:15:57Z

‎Snapins Are Silent

Wayne-workman.28155: /* SnapinPacks are Compressed */

2016-08-30T14:24:25Z

‎SnapinPacks are Compressed

Wayne-workman.28155: /* Examples */

2016-08-28T19:28:21Z

‎Examples

Wayne-workman.28155: /* Examples */

2016-08-28T17:10:38Z

‎Examples

Wayne-workman.28155: /* SnapinPacks are Compressed */

2016-08-28T17:09:14Z

‎SnapinPacks are Compressed

Wayne-workman.28155 at 16:23, 28 August 2016

2016-08-28T16:23:45Z

← Older revision		Revision as of 17:20, 28 October 2016
Line 1:		Line 1:
	Under construction.		Under construction.

		+	See also: [[Snapin Examples]]

	= SnapinPacks Brief Overview =		= SnapinPacks Brief Overview =

@@ Line 54: / Line 54: @@
 * PowerShell 3 and above: <font color="red">$PSScriptRoot</font>
 * Batch Scripts: <font color="red">%~dp0</font>
 = Creating a SnapinPack =

@@ Line 41: / Line 41: @@
 <font color="red">C:\Program Files (x86)\FOG\tmp\common-things\install.msi</font>
 The file we wish to run is <font color="red">run.bat</font>. In the SnapinPack configuration, we see the field "Snapin Pack Arguments". If you have used the template for SnapinPacks, and then chosen an appropriate template for what type of executable, this field will be filled in for you mostly, but you must still edit it.
 In this case, we want to run a batch file, so after selecting the Snapin Type's SnapinPack choice and then picking the Snapin Pack Template's Batch File choice, we find that the Snapin Pack Arguments is filled in with <font color="red">/c "[FOG_SNAPIN_PATH]\MyScript.bat"</font>.
@@ Line 48: / Line 48: @@
 Of course, in this example, we don't want to run "MyScript.bat" because it doesn't exist. We want to execute <font color="red">run.bat</font>. So, we simply edit the Snapin Pack Arguments, remove the generic executable name, and place our desired executable name.
 = Creating a SnapinPack =

@@ Line 14: / Line 14: @@
 = Snapins Run as SYSTEM or root =
-All Snapins including SnapinPacks run as the <font color="red">SYSTEM</font> or <font color="red">root</font> user's security context. If a snapin or SnapinPack runs successfully by manual execution but not via the FOG Client - this is typically related to the security context. For example, say you have a shared directory that is granted read access for all <font color="red">Domain Users</font>. Well, an individual host's local <font color="red">SYSTEM</font> or <font color="red">root</font> account is not a member of <font color="red">Domain Users</font>. Therefore, unless alternative credentials are supplied to access the share, any script executed that tries to read this share will not work. There are a few solutions to this. Granting the share read access for anonymous users is the most simple. Specifying credentials within scripts, or as arguments are viable options.
+All Snapins including SnapinPacks run as the <font color="red">SYSTEM</font> or <font color="red">root</font> user's security context. If a snapin or SnapinPack runs successfully by manual execution but not via the FOG Client - this is typically related to the security context. For example, say you have a shared directory that is granted read access for all <font color="red">Domain Users</font>. Well, an individual host's local <font color="red">SYSTEM</font> or <font color="red">root</font> account is not a member of <font color="red">Domain Users</font>. Therefore, unless alternative credentials are supplied to access the share, any script executed that tries to read this share will not work. There are a few solutions to this. Granting the share read access for anonymous users is the most simple. Specifying credentials within scripts or as arguments are viable options.
 = SnapinPacks are Compressed =

@@ Line 10: / Line 10: @@
 = Snapins Are Silent =
-SnapinPacks must be silent, this requirement has not changed. What is a silent snapin? A silent snapin requires zero interaction to run. If at any point the snapin asks for input from a user, it will simply wait for input that will never come, and timeout eventually.
+SnapinPacks must be silent, this requirement has not changed. What is a silent snapin? A silent snapin requires zero interaction to run. If at any point the snapin asks for input from a user, it will simply wait for input that will never come, and indefinitely hang.
 = Snapins Run as SYSTEM or root =

← Older revision		Revision as of 14:24, 30 August 2016
Line 36:		Line 36:

	<font color="red">C:\Program Files (x86)\FOG\tmp\common-things\run.bat</font>		<font color="red">C:\Program Files (x86)\FOG\tmp\common-things\run.bat</font>
		+
		+	and
		+
	<font color="red">C:\Program Files (x86)\FOG\tmp\common-things\install.msi</font>		<font color="red">C:\Program Files (x86)\FOG\tmp\common-things\install.msi</font>

@@ Line 110: / Line 110: @@
 External Video Link:
-[https://www.youtube.com/watch?v=vIGbm5wvMC4 Chrome SnapinPack FOG 1 3 0 Example and Explanation ]
+[https://www.youtube.com/watch?v=vIGbm5wvMC4 Chrome SnapinPack FOG 1.3.0 Example and Explanation ]
 Video:
 <embedvideo service="youtube">https://www.youtube.com/watch?v=vIGbm5wvMC4</embedvideo>
-== MSI ==
+== Batch Script - deploy wireless profile ==
 == BASH Script ==

@@ Line 106: / Line 106: @@
 = Examples =
-== Very thorough Batch Script example ==
+== Very thorough example ==
 External Video Link:

@@ Line 24: / Line 24: @@
 If the .zip file extracts a folder with files, this internal folder's name does not change, but it is still all placed within a parent directory named with the SnapinPack's name. For instance, if I had a SnapinPack called "<font color="red">abc</font>", and I uploaded a .zip file to the FOG server for it called "<font color="red">def.zip</font>", and within that .zip file there was a folder called "<font color="red">ghi</font> and within that folder, a file called "<font color="red">jkl.bat</font>".
-* The FOG Client would create a directory called "<font color="red">C:\Program Files (x86)\FOG\tmp\abc</font>"
+* The FOG Client would create a directory called "C:\Program Files (x86)\FOG\tmp<font color="red">\abc</font>"
 * The FOG Client would extract everything in the .zip file into the above path.
-* The folder inside the .zip file is now at "<font color="red">C:\Program Files (x86)\FOG\tmp\abc\ghi</font>"
+* The folder inside the .zip file is now at "C:\Program Files (x86)\FOG\tmp<font color="red">\abc\ghi</font>"
-* The executable's path would be "<font color="red">C:\Program Files (x86)\FOG\tmp\abc\ghi\jkl.bat</font>"
+* The executable's path would be "C:\Program Files (x86)\FOG\tmp<font color="red">\abc\ghi\jkl.bat</font>"
-* The FOG Client's variable <font color="red">[FOG_SNAPIN_PATH]</font> for this SnapinPack expands to "<font color="red">C:\Program Files (x86)\FOG\tmp\abc</font>" at runtime.
+* The FOG Client's variable <font color="red">[FOG_SNAPIN_PATH]</font> for this SnapinPack expands to "C:\Program Files (x86)\FOG\tmp<font color="red">\abc</font>" at runtime.
 * To path further past the <font color="red">[FOG_SNAPIN_PATH]</font> variable, just append after it as in the provided example, include any folder paths, and the desired executable.

@@ Line 102: / Line 102: @@
 * '''13.''' Click the "ADD" button at the bottom when you are satisfied with your SnapinPack.
-== Deploying a Snapin ==
+== Deploying a SnapinPack ==
 = Examples =
 == MSI ==