Step1: Download wget : http://gnuwin32.sourceforge.net/packages/wget.htm
Step2: run the following command
wget -m http://<weburl/>
Step 2.1 : If you want to download only say pdf files from the url then use the following command
wget -m -A pdf http://<weburl/>
Thats it.
Yesterday, I came accross a very funny error, A friend of mine told me that he has published a sequence on two servers and the package is working fine on one server but fails when streamed from another server and user is getting “Not Authorised Error”.
This is a very common error while streaming and is mostly generated when the sequence is not published on the server. But in this case it was published.
After struggling for two hour, I found that my friend was testing the seq which was published on two servers on same client machine without cleaning the cache. I asked him to cleanup the cache and then try again, but this time launch the osd from the server which is not working. After few mins he called me and said that now it is working fine.
Issue:
The issue was that when he launched the osd from Server A, the OSD file got cached in alluser profile and then when he launched it from Server , it went to server A and was trying to launch it from there and thats were all the hell broke down.
Lesson’s Learned:
Always clean the cache using lucy (my softgrid client helper) or through the softgrid client console, and then do the testing for another package.
Application Size: If the maximum client cache size is set for 4 GB (The Max can be 64 GB), then the maximum size of application (sft file) which can be streamed on that machine is 4 GB.
All applications which have the installed footprint greater then or equal to the max client size, set by the client, should not be sequenced. The Max applicaiton size Softgrid can handle is 4GB, [This is my guess as Q: drive has FAT filetype and the max filesize FAT can handle is 4GB ] {NEEDS to be verified by Microsoft.} More details at http://www.softgridguru.com/viewtopic.php?t=2763.
Device Driver: Softgrid presently do not support sequencing of device drivers thus any application which install device driver should not be sequenced.
The only exception is when the device driver can be installed locally without installing the application. In this case the Device driver should be installed locally and only the application without the device driver should be sequenced.
Shortcuts: Application should have minimum of 1 Shortcut. If no shortcuts are present then the application should be sequenced in a Suite along with the application which needs it.
If Macromedia Flash is the application in question to be sequenced then the shortcut should be pointing to the locally installed IE.
Middleware: Middleware applications are not a good candidate for sequencing as they can be used as prerequisites by various many applications in the build and thus should be installed locally. but if multiple version of it are needed then it should be sequenced along with the application which needs them.
Path hard coding: The application should not have folder/file path hard coded in the application itself. Some application hard code the path of files in registry or ini file or executables.
In these cases it has been found that the application can be sequenced most of the time, but extreme care should be taken while sequencing & testing. Configuration files such as ini, conf, txt etc are good places to look for the hardcoding.
Base Build Applications: Applications which are already part of base build should not be sequenced. One can sequence them but they are of no real value.
Auto Update: Application with automatic updates should not be sequenced. Sequenced application most of the time fails to properly update itself. Also allowing auto update leads to non compliance of application version.
Application should be sequenced only if the auto update feature can be disabled during sequencing procedure.
Services: For services -item, you should note that services that can be started when application starts and shut down when application main executable shuts down can be included in sequence. Only services that run as their own are (like boot-time services do but there are others) not suitable for sequencing since under SoftGrid all application starting happens under user’s session context. Special thanks to ksaunam.
COM+: Some application which uses COM+ might not work properly in virtual environment, thus this type of applications needs be tested properly.
COM DLL: Few application which uses COM DLL surrogate virtualization, i.e. DLL’s that run in Dllhost.exe, does not work properly in Softgrid Environment. Thus this type of applications needs be tested properly.
Licensing Policies: Applications with licensing enforcement tied to machine, e.g. the license is tied to the system’s MAC address. This type of application should not be sequenced if the activation can not be done by the user at the first launch of sequenced application.
I have only seen this error message under following conditions.
