| Author |
Message |
| tzuk |
Posted: Sun Feb 22, 2009 9:41 pm Post subject: |
|
| It's a new page so you could not have found it earlier. You can now find links to this new page in the Download page and the Commercial Licensing page. |
|
 |
| Kay |
Posted: Sun Feb 22, 2009 2:50 am Post subject: |
|
thank you for youre help tzuk
I will try it mondays, but I think that was the problem.
The page about the Corporate Installation is also very nice, thanks for that.
I never saw that tutorial, under which point of youre website did I find the link for this tutorial?
once again, thank you for youre help  |
|
 |
| tzuk |
Posted: Fri Feb 20, 2009 2:19 pm Post subject: |
|
| Kay wrote: |
| But the Problem really is there, and you can check it easy with my installation script and my configuration above. Of course its really important that there is NO configuration file at C:\Windows. |
Kay, I tried your approach, and fortunately I could reproduce the problem. But it turns out it happened to me because the "template" that I created Sandboxie.ini was not UNICODE. So Sandboxie was just ignoring it.
Please check the Event Viewer and check the System log for any warnings from Sandboxie regarding the configuration file. And keep in my mind the requirement for UNICODE encoding.
| Kay wrote: |
| No I just updated the configuration file. The right place for the SbieCtrl_Xxx is only UserSettings_Xxx ? I want that any new user uses the SbieCtrl_Xxx Settings at the [DefaultBox]. |
Then put them in [UserSettings_Default]. I've addressed this point, and several others that you might find interesting, in a new page advising how to do a corporate install. Please take a look.
http://www.sandboxie.com/index.php?CorporateInstallation |
|
 |
| wraithdu |
Posted: Fri Feb 20, 2009 2:13 pm Post subject: |
|
| I think tzuk has made it clear that there is only one place that is appropriate for SbieCtrl_Xxx settings. Use the GUI for your configuration instead of hand editing the INI to prevent errors like this. |
|
 |
| Kay |
Posted: Fri Feb 20, 2009 8:07 am Post subject: |
|
| tzuk wrote: |
| Very well, I will try as you suggest and post an update. I am however curious why once again the SbieCtrl_Xxx settings appear in a section that is not a [UserSetings_Xxx] section. This time they are in your [DefaultBox] section. Last time it was part of the [GlobalSettings] section. Is this a copy/paste oversight? |
Ok thanks
No I just updated the configuration file. The right place for the SbieCtrl_Xxx is only UserSettings_Xxx ? I want that any new user uses the SbieCtrl_Xxx Settings at the [DefaultBox]. |
|
 |
| tzuk |
Posted: Thu Feb 19, 2009 7:35 pm Post subject: |
|
| Very well, I will try as you suggest and post an update. I am however curious why once again the SbieCtrl_Xxx settings appear in a section that is not a [UserSetings_Xxx] section. This time they are in your [DefaultBox] section. Last time it was part of the [GlobalSettings] section. Is this a copy/paste oversight? |
|
 |
| Kay |
Posted: Thu Feb 19, 2009 1:49 pm Post subject: |
|
| tzuk wrote: |
| Kay wrote: |
| thats not the point, sandboxie control or service. |
Well in fact it was entirely my point. The INI file is written by the service, and the service is running under the Local System (SYSTEM) account. Is it possible your SYSTEM account can't access C:\Windows? Highly unlikely.
In any case if you want to put the file in C:\Program Files\Sandboxie then just make sure
(1) that there is such file in C:\Program Files\Sandboxie
(2) that there isn't such file in C:\Windows
(3) and then Reload Configuration |
Yes youre right about the fact that the SYSTEM account, it can access c:\windows, that was my fault.
(1) yes 100% sure
(2) yes 100% sure
(3) done with reboot
But the Problem really is there, and you can check it easy with my installation script and my configuration above. Of course its really important that there is NO configuration file at C:\Windows.
If theres just a configurationfile at C:\Program Files\Sandboxie you got problems with editadminonly. Please give it a try, thank you |
|
 |
| tzuk |
Posted: Tue Feb 17, 2009 4:35 pm Post subject: |
|
| Kay wrote: |
| thats not the point, sandboxie control or service. |
Well in fact it was entirely my point. The INI file is written by the service, and the service is running under the Local System (SYSTEM) account. Is it possible your SYSTEM account can't access C:\Windows? Highly unlikely.
In any case if you want to put the file in C:\Program Files\Sandboxie then just make sure
(1) that there is such file in C:\Program Files\Sandboxie
(2) that there isn't such file in C:\Windows
(3) and then Reload Configuration |
|
 |
| Kay |
Posted: Tue Feb 17, 2009 3:38 pm Post subject: |
|
thats not the point, sandboxie control or service.
Sandboxie itself(its service or the control) wants to write a configuration to C:\windows and that is the issue of the error messages. I copied the configuration files to the directory c:\programs\sandboxie and my user has no rights to handle the configuration file at the location of c:\windows.
It finds Sandboxie.ini at C:\Program Files\Sandboxie but wants to write it to C:\Windows
| Quote: |
Location
Sandboxie looks for the file Sandboxie.ini in the following folders, in this order:
* In the Windows folder: C:\WINDOWS on most Windows installation; C:\WINNT on Windows 2000
* In the Sandboxie installation folder: Typically C:\Program Files\Sandboxie
The search for Sandboxie.ini ends when an instance of the file is found, and all other instances are ignored.
When Sandboxie Control updates the configuration, it rewrites the file Sandboxie.ini file in the folder from which the configuration was last read.
|
batch installation file that gets these error messages, I described:
mkdir C:\Programme\Sandboxie\Sandbox
mkdir C:\Programme\Sandboxie\
xcopy \\serverXY\Sandboxie\Sandboxie.ini C:\Programme\Sandboxie /R /Y
\\serverXY\Sandboxie\SandboxieInstall /install /S /D=C:\Programme\Sandboxie |
batch installation file that gets NO error messages:
mkdir C:\Programme\Sandboxie\Sandbox
mkdir C:\Programme\Sandboxie\
xcopy \\serverXY\Sandboxie\Sandboxie.ini C:\Programme\Sandboxie /R /Y
xcopy \\serverXY\Sandboxie\Sandboxie.ini C:\Windows /R /Y
\\serverXY\Sandboxie\SandboxieInstall /install /S /D=C:\Programme\Sandboxie |
thats the Sandboxie.ini
[GlobalSettings]
EditAdminOnly=yes
BoxRootFolder=C:\Programme\Sandboxie\Sandbox
AutoDelete=yes
[DefaultBox]
BoxRootFolder=C:\Programme\Sandboxie\Sandbox
AutoDelete=yes
AutoRecoverIgnore=.jc!
AutoRecoverIgnore=.part
LingerProcess=trustedinstaller.exe
LingerProcess=wuauclt.exe
LingerProcess=devldr32.exe
LingerProcess=syncor.exe
LingerProcess=jusched.exe
LingerProcess=acrord32.exe
Enabled=y
OpenFilePath=iexplore.exe,%Favorites%
OpenFilePath=X:\WORK\DOWNLOADS
OpenFilePath=%Personal%\WORK\DOWNLOADS
ConfigLevel=4
CopyLimitKb=32000
SbieCtrl_ShowWelcome=N
SbieCtrl_NextUpdateCheck=1555555555
SbieCtrl_UpdateCheckNotify=N
SbieCtrl_BoxExpandedView_DefaultBox=N
SbieCtrl_WindowLeft=358
SbieCtrl_WindowTop=202
SbieCtrl_WindowWidth=660
SbieCtrl_WindowHeight=450
SbieCtrl_Hidden=Y
SbieCtrl_ActiveView=40021
SbieCtrl_AutoApplySettings=Y
SbieCtrl_ColWidthProcName=250
SbieCtrl_ColWidthProcId=70
SbieCtrl_ColWidthProcTitle=310
SbieCtrl_EnableLogonStart=Y
SbieCtrl_EnableAutoStart=Y
SbieCtrl_AddDesktopIcon=N
SbieCtrl_AddQuickLaunchIcon=N
SbieCtrl_AddContextMenu=N
SbieCtrl_AddSendToMenu=N
SbieCtrl_TerminateNotify=N
SbieCtrl_TerminateWarn=N
SbieCtrl_ExplorerNotify=N
SbieCtrl_ExplorerWarn=N
SbieCtrl_EditConfNotify=N
SbieCtrl_ReloadConfNotify=N
SbieCtrl_HideWindowNotify=N
SbieCtrl_ProcSettingsNotify=N
SbieCtrl_SettingChangeNotify=N
SbieCtrl_ShortcutNotify=N
BoxNameTitle=n
BorderColor=#FF0000
|
|
|
 |
| tzuk |
Posted: Sat Feb 14, 2009 1:53 pm Post subject: |
|
| Sandboxie Control never writes to Sandboxie.ini directly, regardless of the location of the INI file. Modifications always go through the Sandboxie service. So I think you can put back Sandboxie.ini in C:\Windows. |
|
 |
| Kay |
Posted: Fri Feb 13, 2009 3:22 pm Post subject: |
|
I modified the configuration, but that was not the issue.
I think the problem is, that sandboxie still wants a configuration file at c:\windows or wants to write one to this directory.
But my "normal user" is a AD user with no rights to do this. And the sandboxie.ini is at the sandboxie directory but however, it still wants to write one at the windows directory and that is key of this problem overall. Can i tell sandboxie NEVER write a configuration file to c:\windows ? |
|
 |
| tzuk |
Posted: Mon Feb 02, 2009 11:03 pm Post subject: |
|
| I see what you mean, Guest10. You're probably right. But in that case I have nothing to guess as the cause of the problem that Kay is seeing. |
|
 |
| Guest10 |
Posted: Mon Feb 02, 2009 11:00 pm Post subject: |
|
Actually, I think his configuration file is just missing a couple of lines, not that settings have been added to the Global section.
Possibly, he deleted the [UserSettings_xxxxxxx] line and the SbieCtrl_UserName=xxxxxx lines before posting?
[GlobalSettings]
EditAdminOnly=no
BoxRootFolder=C:\Programme\Sandboxie\Sandbox
[UserSettings_xxxxxxx]
SbieCtrl_UserName=xxxxx
SbieCtrl_ShowWelcome=N
SbieCtrl_NextUpdateCheck=1555555555
... |
|
 |
| tzuk |
Posted: Mon Feb 02, 2009 9:39 pm Post subject: |
|
I looked at it now, but could not reproduce the problem. I followed these steps:
First, I edited Sandboxie.ini from an Administrator user, and I made sure the configuration file contains this:
[GlobalSettings]
EditAdminOnly=yes
[DefaultBox]
...
...
[UserSettings_XXXXXXXX]
SbieCtrl_UserName=MyAdminUser
...
...
|
Then I logged into a newly created standard user and started Sandboxie Control. There were no errors and the configuration file was updated with a new section at the bottom:
[UserSettings_YYYYYYYY]
SbieCtrl_UserName=MyOtherUser
...
...
|
And as a secondary test, I tried altering sandbox settings from this non-admin account that I was no logged into, and I got the error message that it is not allowed because I am not admin.
Bottom line: I'm not seeing the problem you describe. Perhaps the problem has something to do with you putting SbieCtrl_ lines in GlobalSettings, as soccerfan noted earlier. Try to remove those lines and then see if the problem is resolved. |
|
 |
| Kay |
Posted: Mon Feb 02, 2009 1:45 pm Post subject: |
|
| tzuk wrote: |
| Quote: |
| EditAdminOnly=yes from the beging, I login in with the non admin user. Sandboxie gives me a lot of error messages, cauze it cant write an user section to the Sandboxie.ini. I hope you understood my problem. |
The UserSettings section should not be affected by EditAdminOnly. Or at least that was the idea. I will try a look at this problem to see if it no longer works as I expect. |
Do you had time to look at the problem? |
|
 |