bob.BLOG.ja

In Place Upgrade To LTSB 2016
=============================
Change EditionID and ProductName at registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
EditionID = EnterpriseS
ProductName = Windows 10 Enterprise S

Then just run setup.exe from LTSB ISO (extracted to a temp folder somewhere).

http://blog.switchsystems.co.uk/2014/01/reducing-memory-usage-on-sbs-servers/

Lately we’ve been having some very sluggish performance out-of-the-box from some SBS servers, so i’ve been tweaking some configurations to make the servers perform a bit better. Things like:

• Limiting store.exe (Exchange Information Store) memory usage
• Limiting Sharepoint database memory usage
• Limiting WSUS database memory usage
• Making Remote Web Workspace “Connect to computer” work when 0 memory is available

Follow the steps below to tune your memory usage – and be warned, if you do things incorrectly then you can actually decrease the performance of your server!

Exchange and store.exe

You probably know that store.exe will normally just consume all available memory until the system decies that something else uses it, then it tries to relinquish that allocated memory. In practice we’ve found that this comes at a performance hit for other programs, so here’s how to limit the amount of memory store.exe utilises:

Overview: Use ADSIedit.msc to update msExchESEParamCacheSizeMin and msExchESEParamCacheSizeMax with page sizes.

1. Run adsiedit.msc
2. Connect to: Select a well known Naming Context : [Configuration]
3. Expand the following:
   • Configuration\Services\Microsoft Exchange\ (First Organization) \Administrative Groups\ (Exchange Administrative Group) \Servers\ (Server Name)
4. Right click on CN=Information Store and click properties
5. Update the values of msExchESEParamCacheSizeMin and msExchESEParamCacheSizeMax with values from the following table:
   

   Target Cache Size in GB	msExchESEParamCacheSize for 2010+ (32KB pages)	msExchESEParamCacheSize for 2007 (8KB pages)
   1	32768	131072
   2	65536	262144
   3	98304	393216
   4	131072	524288
   6	196608	786432
   8	262144	1048576
   10	327680	1310720
   12	393216	1572864
   14	458752	1835008
   16	524288	2097152
   18	589824	2359296
   20	655360	2621440

   Source: http://meridian.ws/wordpress/?p=239
6. Restart the Information Store service for the changes to take affect.

Sharepoint MSSQL database

The obvious use-case for most businesses is to just disable the service, as we don’t know anyone who runs SBS and actually uses Sharepoint, but if you do, you can limit it’s memory usage via the SQL Management Studio.

1. Run the SQL Server Management Studio program (should be in Programs -> Microsoft SQL Server 2008 [R2]) from an ELEVATED ADMINISTRATOR session (right click on the shortcut and do ‘run as administrator’)
2. Connect to: [SERVERNAME]\Sharepoint , using Windows Authentication
3. Right click on the SQL server at the top of the tree view and select properties
4. Goto the Memory section and then type in a value for “Maximum server memory (in MB)”
   It’s a good idea to first check how much memory it’s currently using via the task manager!
5. Click OK
6. Restart the SQL Service

WSUS Database

We’re going to do exactly the same thing for the WSUS database. It’s actually on it’s own “windows internal database” and not MSSQL Server, and it won’t allow TCP connections by default – this means we have to use a named pipe of \\.\pipe\mssql$microsoft##ssee\sql\query to connect to it.

1. Run the SQL Server Management Studio program (should be in Programs -> Microsoft SQL Server 2008 [R2]) from an ELEVATED ADMINISTRATOR session (right click on the shortcut and do ‘run as administrator’)
2. Connect to: \\.\pipe\mssql$microsoft##ssee\sql\query , using Windows Authentication
3. Right click on the SQL server at the top of the tree view and select properties
4. Goto the Memory section and then type in a value for “Maximum server memory (in MB)”
   It’s a good idea to first check how much memory it’s currently using via the task manager!
5. Click OK
6. Restart the SQL Service

Configuring Remote Web Workspace

Since the .net 4.5.1 framework update, there may be problems launching .net processes out of IIS – this is due to some memory checking that now happens which checks that you have at least 5% free memory. The following error is logged in the event log:

Exception type: InsufficientMemoryException
Exception message: Memory gates checking failed because the free memory (xxxx bytes) is less than 5% of total memory. 
As a result, the service will not be available for incoming requests. 
To resolve this, either reduce the load on the machine or 
adjust the value of minFreeMemoryPercentageToActivateService on the serviceHostingEnvironment config element.

This can be fixed by performing the following:

• Open web.config file located at: “%ProgramFiles%\Windows Small Business Server\Bin\WebApp\RemoteAccess”.
• Search in Web.config for “<serviceHostingEnvironment aspNetCompatibilityEnabled=”true” />”, change this line to “<serviceHostingEnvironment aspNetCompatibilityEnabled=”true” minFreeMemoryPercentageToActivateService=”0″/>
• Save changes and close the file.
• Run IISRESET from an elevated Command Prompt window

Links and Source Articles:

[MS Technet] Exchange 2010 store.exe service takes high memory utilization. 
Limit Exchange 2010 / 2007 Store.exe Memory Usage on a Windows Small Business Server 2011 / 2008
SBS 2011 Exchange Memory Usage Limits with side note for Exchange 2007
Troubleshooting “An unexpected error occurred” message when using Remote Web Access to connect to computers

http://www.digitalruby.com/securing-your-windows-dedicated-server/

Run in powershell:

$obj = gwmi -namespace “Root/CIMV2/TerminalServices” Win32_TerminalServiceSetting
$obj.ChangeMode(4) #(2) for per-device licenses.
$obj.SetSpecifiedLicenseServerList(“LocalServerNameHere”)

and restart the server.

http://itcafe.hu/tema/navon_platinum_explorer_7_android_navigacio/hsz_161-180.html

Hibajelenség: először kevés tárhely hiba jelentkezik és/aztán egymás után lefagyó processzek, majd végül egyáltalán nem indul újra a készülék, “Android logónál” megáll. (Olyan szinten maga alá szemetel a SW, hogy nem tud újraindulni…) Valójában nem áll meg, hanem boot-loop-ba kerül, végtelen hurokba, hibára futva újra-újra indul.
A hiba oka a memória megtelik.
Megoldás:
DDMS-sel (Dalvik Debug Monitor Service) a File Explorer-ben a data\dalvik-cache\ -ben lévő fájlokat kitörölni egyesével, vagyis a dalvik-cache-t kitörölni.
Egyébként minden valamirevaló androidos eszközön van recovery menu, ahol ezt meglehet csinálni, az pedig felháboritó, hogy reset gomb-bal nem lehet a gyári beállitásokat visszatölteni!
Folyamat:
1) ADB driver telepités: http://filetram.com/mediafire/adb-drivers-allwinnera10-32and64-zip-8954671813
2) DDMS telepités, én az Android SDK, java SDK és eclipse telepitéssel csináltam: http://developer.android.com/sdk/index.html vagy http://swguru.hu/android_fejlesztokornyezet_telepitese
fontos, hogy vigyük végig a telepitést pontosan.
3) készülék inditás, ADB driver telepités, Eszközkezelőben Android ADB Device megjelenik
4) Eclipse inditás, Welcome ablak bezárás, ha még nem lenne bezárva
5) Jobb felső sarokban: Open Perspective (ikon kék ablakocska, sárga kis kereszt) –> DDMS (zöld ikon) kiválasztás
6) DDMS ablak megjelenik, bal oldalon Devices, ha csatlakoztatjuk a telefont, akkor megjelenik az eszköz. Jobb oldalon File Explorer
7) File Exlorer-ben tallózzuk be a data\data\dalvik-cache és törölgessük ki belőle a fájlokat.
8) ha jól csináltuk bal oldalon a device alatt látjuk, hogy processzek egymás után indulnak el és végül bebootol a készülék.
9) mentés visszaállitásban végezzük el a gyári beállitások visszaállitását

Viszont, hogy a kedves usernek ne naplózzon tovább ez a csodakütyü, ezt hajtottam végre:
“My fix was easy. I hope it helps you.
Edit gpsconfig.xml found at /system/etc/gps/
Near the top:
cLogEnabled=”true”
to:
cLogEnabled=”false”
Reboot
Delete the log files.”

Ha túl nagyra nő az SBSMonitoring.mdf adatbázis, lelassul a szerver, a DataCollectorSvc.exe rengeteg memóriát eszik.

Az adatbázis újrakreálása:

To recreate the databases use these steps:

1. Download the following package:

https://skydrive.live.com/self.aspx/.Public/MonitoringDBRecreate/Create-SBSMonitoringDb.zip?cid=d5fe25afb6c3615f&sc=documents

1. Extract the files to c:\windows\temp
2. Complete the one set of the following steps according to the version you are working with:

For SBS 2008

1. Launch an administrative PowerShell session
2. Launch the script:
   C:\windows\temp\Create-SBSMonitoringDb.ps1
3. After completing the script and verifying that that monitoring is working, complete the steps in this article:http://blogs.technet.com/b/sbs/archive/2009/07/14/sbs-2008-console-may-take-too-long-to-display-alerts-and-security-statuses-display-not-available-or-crash.aspx

For SBS 2011 Standard

1. Launch “C:\Program Files\Windows Small Business Server\Bin\MoveDataPowerShellHost.exe” as an administrator
2. Launch the script:
   C:\windows\temp\Create-SBSMonitoringDb.ps1

Trouble Shooting:

File C:\windows\temp\create-sbsmonitoringdb.ps1 cannot be loaded because the execution of scripts is disabled on this system. Please see “get-help about_signing” for more details.
By default we should have the required code execution policy on our SBS servers, this issue is usually related to the way the script was downloaded into the affected server. Open the properties of the download script file from Windows Explorer and click on the Unblock option.

forrás:

http://blogs.technet.com/b/sbs/archive/2011/08/22/how-to-recreate-the-sbsmonitoring-database.aspx

Create-SBSMonitoringDb

A windows 7 alkalmas szoftveres wifi AP létrehozására.

Ehhez néhány netsh parancs kell csak:

(parancssor rendszergazdaként)

netsh wlan set hostednetwork mode=allow ssid=a hálózat neve key=jelszó

Ezután megjelenik a hálózati kártyák között egy microsoft virtual wifi miniport adapter.

A hálózati adaptereknél válasszuk ki azt az adaptert, amivel a gépünk az internetre kapcsolódik, a tulajdonságokban állítsuk be az internet kapcsolat megosztást.

Otthoni hálózat kapcsolatnak válasszuk ki a microsoft virtual wifi miniport adaptert.

Ezután ismét parancssor:

netsh wlan start hostednetwork

Ha esetleg nem lehet belépni a létrejött wifi hálózatba, meg kell próbálni újra az egészet.

A megosztás megmarad, azt nem kell bántani.

Parancsok, amik kapcsolatosak a témával:

most már nekem is van bolg-om
de minek?